IEEE-SA Search Results
Date
Anytime
30 Days
60 Days
90 Days
180 Days
1 Year
2 Years
Specific Date
Format
All
HTML
XML
PDF
Microsoft Word
Microsoft PowerPoint
Microsoft Excel
Plain Text
Other
944 results found. results are sorted by relevance
1-25
https://grouper.ieee.org/groups/802/802_tutorials/04-July/802.15.3%20PAL%201394.pdf
Protocol Adaptation Layer (PAL) for IEEE 1394 over IEEE 802.15.3 Protocol Adaptation Layer (PAL) for IEEE 1394 over IEEE 802.15.3 (“wireless 1394”) Peter Johansson Congruent Software, Inc.
https://grouper.ieee.org/groups/802/15/pub/2004/15-04-0523-00-0000-1394-trade-association-liaison-report.pdf
The 1394 Trade Association approves the WiMedia Alliance's MAC Convergence Architecture (WiMCA) as a platform for "wireless 1394" PAL development. 2.
https://grouper.ieee.org/groups/802/15/pub/04/15-04-0523-00-0000-1394-trade-association-liaison-report.pdf
The 1394 Trade Association approves the WiMedia Alliance's MAC Convergence Architecture (WiMCA) as a platform for "wireless 1394" PAL development. 2.
https://grouper.ieee.org/groups/1722/contributions/2007/avbtp-boatright-sync_usage_cases-2007-9-17.pdf
AVB Synchronization Usage Cases IEEE P1722 Working Group 17 Sep 07 AVB Synchronization Usages IEEE P1722 Working Group 17 Sep 07 Robert Boatright rboatright@harman.com AVB-AVB Synchronization AVB Endpoint AVB Bridge AVB Bridge AVB Endpoint AVB Endpoint Word clock Word clock Sample & Phase coherent clocks Word clock IEEE 1394 to AVB Synchronization AVB Endpoint AVB Bridge AVB Bridge AVB Endpoint AVB Endpoint Word clock Word clock Sample & Phase coherent clocks Word clock 1394Device 1394 Gateway Device IEEE 1394-to-IEEE 1394 Synchronization AVB Endpoint AVB Bridge AVB Bridge AVB Endpoint Word clock Word clock Sample & Phase coherent clocks Word clock 1394Device 1394 Gateway Device AVB Endpoint 1394 Device 1394 Gateway Device AVB-to-IEEE 1394 Synchronization AVB Bridge AVB Bridge AVB Endpoint Word clock Word clock Sample & Phase coherent clocks Word clock AVB Endpoint 1394 Device 1394 Gateway Device AVB Endpoint The challenge... • Present a single implementation for SYT that encompasses all four usage cases AVB Synchronization Usages IEEE P1722 Working Group17 Sep 07 AVB-AVB Synchronization IEEE 1394 to AVB Synchronization IEEE 1394-to-IEEE 1394 Synchronization AVB-to-IEEE 1394 Synchronization The challenge...
https://grouper.ieee.org/groups/802/3/re_study/email/msg00079.html
>> >> It strikes me that the problem of bridging: >> >> <-- IEEE 1394 -->...<-- IEEE 802.3 -->...<-- IEEE 1394 --> >> >> would be best served by: >> >> <-- IEEE 1394 -->...<-- IEEE 1394 -->...<-- IEEE 1394 --> >> >> Hugh. >> Follow-Ups : Re: [RE] What's wrong using FireWire as the home backbone?
https://grouper.ieee.org/groups/1722/contributions/2009/1722_AnnexB.pdf
If an Ethernet AVBTP to IEEE 1394 gateway receives multiple packets for a given cycle and that 1394 network can support large CIP packets, the 1394 gateway shall reassemble the smaller AVBTP based CIP packets into larger IEEE 1394 based CIP packets as necessary.
https://grouper.ieee.org/groups/1722/contributions/2009/avbtp-dolsen-annexB-2009-08-31.pdf
If an Ethernet AVBTP to IEEE 1394 gateway receives multiple packets for a given cycle and that 1394 network can support large CIP packets, the 1394 gateway shall reassemble the smaller AVBTP based CIP packets into larger IEEE 1394 based CIP packets as necessary.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00065.html
Re: [RE] Requirement: Bridging to 1394 Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [RE] Requirement: Bridging to 1394 To : STDS-802-3-RE@xxxxxxxxxxxxxxxxx Subject : Re: [RE] Requirement: Bridging to 1394 From : "Gross, Kevin" < kevin.gross@xxxxxxxxxx > Date : Wed, 1 Sep 2004 15:41:55 -0500 Reply-To : "IEEE 802.3 Residential Ethernet"< stds-802-3-re@xxxxxxxx > Sender : owner-stds-802-3-re@xxxxxxxx Thank you Michael.
https://grouper.ieee.org/groups/802/3/re_study/public/200409/teener_1_0904.pdf
Bridging 1394: a requirement for Residential Ethernet Michael Johas Teener Plumblinks mike@teener.com Plumblinks September 28, 2004 Slide 2 Agenda • 1394 use in the home – Why and how – Current and projected market • Networking 1394 busses – Current solutions – Why Ethernet?
https://grouper.ieee.org/groups/802/3/re_study/email/msg00064.html
[RE] Requirement: Bridging to 1394 Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [RE] Requirement: Bridging to 1394 To : STDS-802-3-RE@xxxxxxxxxxxxxxxxx Subject : [RE] Requirement: Bridging to 1394 From : "Michael D.
https://grouper.ieee.org/groups/1722/contributions/2007/avbtp-bartky-proposed-stream-data-format-v0-00-2007-03-20.pdf
7 start) •Editor’s note: 1394 allows a length of zero in this field.
https://grouper.ieee.org/groups/802/15/pub/04/15-04-0674-00-0000-1394ta-liaison-report.pdf
1394 Trade Association Liaison Report November 2004 Peter Johansson (Congruent Software, Inc.)Slide 1 doc.: IEEE 802.15-04/674r0 Submission Project: IEEE 802.15 Wireless Personal Area Networks (WPANs)Project: IEEE 802.15 Wireless Personal Area Networks (WPANs) Submission Title: [1394 Trade Association Liaison Report] Date Submitted: [16 July, 2004] Source: Peter Johansson (Congruent Software, Inc.) 98 Colorado Ave, Berkeley, CA 94707 (510) 527-3926, (510) 527-3856 FAX, PJohansson@ACM.org Re: 15-04-0674-00-0000-1394TA-Liaison-Report Abstract: Liaison Report from the 1394 Trade Association to IEEE 802.15 Purpose: Maintain liaison between the 1394 Trade Association and IEEE 802.15 Notice: This document has been prepared to assist IEEE 802.15.
https://grouper.ieee.org/groups/802/15/pub/2004/15-04-0674-00-0000-1394ta-liaison-report.pdf
1394 Trade Association Liaison Report November 2004 Peter Johansson (Congruent Software, Inc.)Slide 1 doc.: IEEE 802.15-04/674r0 Submission Project: IEEE 802.15 Wireless Personal Area Networks (WPANs)Project: IEEE 802.15 Wireless Personal Area Networks (WPANs) Submission Title: [1394 Trade Association Liaison Report] Date Submitted: [16 July, 2004] Source: Peter Johansson (Congruent Software, Inc.) 98 Colorado Ave, Berkeley, CA 94707 (510) 527-3926, (510) 527-3856 FAX, PJohansson@ACM.org Re: 15-04-0674-00-0000-1394TA-Liaison-Report Abstract: Liaison Report from the 1394 Trade Association to IEEE 802.15 Purpose: Maintain liaison between the 1394 Trade Association and IEEE 802.15 Notice: This document has been prepared to assist IEEE 802.15.
https://grouper.ieee.org/groups/802/15/pub/05/15-05-0149-00-0000-1394-trade-association-liaison-report.pps
.: IEEE 802.15-05/149r0 Submission Project: IEEE 802.15 Wireless Personal Area Networks (WPANs) Submission Title: [1394 Trade Association Liaison Report] Date Submitted: [18 March, 2005] Source: Peter Johansson (Congruent Software, Inc.) 98 Colorado Ave, Berkeley, CA 94707 (510) 527-3926, (510) 527-3856 FAX, PJohansson@ACM.org Re: 15-05-0149-00-0000-1394TA-Liaison-Report Abstract: Liaison Report from the 1394 Trade Association to IEEE 802.15 Purpose: Maintain liaison between the 1394 Trade Association and IEEE 802.15 Notice: This document has been prepared to assist IEEE 802.15.
https://grouper.ieee.org/groups/802/15/pub/2005/15-05-0149-01-0000-1394-trade-association-liaison-report.pps
.: IEEE 802.15-05/149r0 Submission Project: IEEE 802.15 Wireless Personal Area Networks (WPANs) Submission Title: [1394 Trade Association Liaison Report] Date Submitted: [18 March, 2005] Source: Peter Johansson (Congruent Software, Inc.) 98 Colorado Ave, Berkeley, CA 94707 (510) 527-3926, (510) 527-3856 FAX, PJohansson@ACM.org Re: 15-05-0149-00-0000-1394TA-Liaison-Report Abstract: Liaison Report from the 1394 Trade Association to IEEE 802.15 Purpose: Maintain liaison between the 1394 Trade Association and IEEE 802.15 Notice: This document has been prepared to assist IEEE 802.15.
https://grouper.ieee.org/groups/802/15/pub/05/15-05-0149-01-0000-1394-trade-association-liaison-report.pps
.: IEEE 802.15-05/149r0 Submission Project: IEEE 802.15 Wireless Personal Area Networks (WPANs) Submission Title: [1394 Trade Association Liaison Report] Date Submitted: [18 March, 2005] Source: Peter Johansson (Congruent Software, Inc.) 98 Colorado Ave, Berkeley, CA 94707 (510) 527-3926, (510) 527-3856 FAX, PJohansson@ACM.org Re: 15-05-0149-00-0000-1394TA-Liaison-Report Abstract: Liaison Report from the 1394 Trade Association to IEEE 802.15 Purpose: Maintain liaison between the 1394 Trade Association and IEEE 802.15 Notice: This document has been prepared to assist IEEE 802.15.
https://grouper.ieee.org/groups/802/15/pub/2005/15-05-0149-00-0000-1394-trade-association-liaison-report.pps
.: IEEE 802.15-05/149r0 Submission Project: IEEE 802.15 Wireless Personal Area Networks (WPANs) Submission Title: [1394 Trade Association Liaison Report] Date Submitted: [18 March, 2005] Source: Peter Johansson (Congruent Software, Inc.) 98 Colorado Ave, Berkeley, CA 94707 (510) 527-3926, (510) 527-3856 FAX, PJohansson@ACM.org Re: 15-05-0149-00-0000-1394TA-Liaison-Report Abstract: Liaison Report from the 1394 Trade Association to IEEE 802.15 Purpose: Maintain liaison between the 1394 Trade Association and IEEE 802.15 Notice: This document has been prepared to assist IEEE 802.15.
https://grouper.ieee.org/groups/802/802_tutorials/04-July/1394HistoryAndMarket.pdf
IEEE 1394 Tutorial Agenda • 1394 History and Market • Technical Summary of 1394 • 1394c: 1394/802.3 coexistence • 1394/802.15.3 cooperation • Future cooperation IEEE 1394 History and Market Summary Michael Johas Teener Chair P1394c WG mike@teener.com Agenda • History • Current market • Developing markets Prehistory: 1986-87 • IEEE Study Group started September 1986 – Too many different serial busses .… – IEEE Working Group approved December 1986 – First paper, "Reducing the Tower of Babel", January 1987 • Basic design set by January 1987 – Cable (10m) and backplane environments – 2 Mbaud/sec base rate, 8 Mbaud/sec optional high-speed rate – Bit-serial arbitration, 4B5B data encoding – Guaranteed latency – Read/write/lock transactions with 32-bit address space – Cost for silicon/connector/cable of < $15 • Draft 1.0, November 1987 System support begins: 1988-91 • Apple starts full scale development – Isochronous data a requirement for digital sound – Data rates of 12.288 and 49.152 Mbaud/sec, 4B5B optical interface • IBM and Apple want a better SCSI – Data rates up to 49 Mbaud/sec, 196 MBaud/sec growth – Apple works on optical interface, invents LVDS instead • separate clock, drops 4B5B encoding • Higher layers become robust – 64-bit addressing adopted – DMA control for disk drives • Actual implementations!
https://grouper.ieee.org/groups/802/3/re_study/email/msg00082.html
>>> >>> > >To me, splitting the marketplace and excluding 802.3 from rapid >expansion of the CE marketplace are the main disadvantages of >wiring the home with 1394. > > > > >>>It strikes me that the problem of bridging: >>> >>><-- IEEE 1394 -->...<-- IEEE 802.3 -->...<-- IEEE 1394 --> >>> >>>would be best served by: >>> >>><-- IEEE 1394 -->...<-- IEEE 1394 -->...<-- IEEE 1394 --> >>> >>> > >That's an approach, and it has its advocates.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00081.html
>> > >> > It strikes me that the problem of bridging: >> > >> > <-- IEEE 1394 -->...<-- IEEE 802.3 -->...<-- IEEE 1394 --> >> > >> > would be best served by: >> > >> > <-- IEEE 1394 -->...<-- IEEE 1394 -->...<-- IEEE 1394 --> >> > >> > Hugh. >> > >> References : Re: [RE] What's wrong with FireWire?
https://grouper.ieee.org/groups/802/3/re_study/email/msg00080.html
> > It strikes me that the problem of bridging: > > <-- IEEE 1394 -->...<-- IEEE 802.3 -->...<-- IEEE 1394 --> > > would be best served by: > > <-- IEEE 1394 -->...<-- IEEE 1394 -->...<-- IEEE 1394 --> > > Hugh. > Follow-Ups : Re: [RE] What's wrong with FireWire?
https://grouper.ieee.org/groups/1722/contributions/2007/avbtp-bartky-proposed-stream-data-format-v0-01-2007-03-21.pdf
7 start) •Editor’s note: 1394 allows a length of zero in this field.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00145.html
2) Bridging to 1394 is pretty stringent and may be  re-inventing the 1394 bridge wheel.  
https://grouper.ieee.org/groups/802/3/re_study/email/msg00076.html
It strikes me that the problem of bridging: <-- IEEE 1394 -->...<-- IEEE 802.3 -->...<-- IEEE 1394 --> would be best served by: <-- IEEE 1394 -->...<-- IEEE 1394 -->...<-- IEEE 1394 --> Hugh.
https://grouper.ieee.org/groups/802/3/re_study/email/msg00144.html
2) Bridging to 1394 is pretty stringent and may be  re-inventing the 1394 bridge wheel.