From bugmaster at FreeBSD.org Mon Nov 2 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 2 11:07:53 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200911021106.nA2B6qTB033564@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139549 firewire [firewire] reconnecting a firewire disk does not cause o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total. From js at alien8.de Tue Nov 3 12:03:06 2009 From: js at alien8.de (Julian Stecklina) Date: Tue Nov 3 12:03:13 2009 Subject: Bootable Firewire Drives References: <1256762062.2790.17.camel@Lappy> Message-ID: <87tyxbhl3z.fsf@tabernacle.localhost> Sean Bruno writes: > Does anyone have a good idea of what(if any) motherboard bios' support > firewire as a bootable target? > > None of my machines seem to be able to boot off an external firewire > drive which is hampering my efforts to prove out the code. It could be implemented as Option ROM on a Firewire controller, regardless of the BIOS. I haven't seen one, though. Regards, -- Julian Stecklina The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners - Ernst Jan Plugge From bugmaster at FreeBSD.org Mon Nov 9 11:06:50 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 9 11:07:52 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200911091106.nA9B6oeU078966@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139549 firewire [firewire] reconnecting a firewire disk does not cause o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total. From bugmaster at FreeBSD.org Mon Nov 16 11:06:51 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 16 11:07:54 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200911161106.nAGB6ouM011139@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139549 firewire [firewire] reconnecting a firewire disk does not cause o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total. From freebsd at sopwith.solgatos.com Tue Nov 17 05:33:08 2009 From: freebsd at sopwith.solgatos.com (Dieter) Date: Tue Nov 17 05:33:15 2009 Subject: VIA firewire controller and "non CYCLEMASTER mode" Message-ID: <200911162013.UAA01961@sopwith.solgatos.com> It has been over a year, time to ask again: > If we assume that I need to get the VIA into non-CYCLEMASTER mode, > (since that worked with the NEC), any ideas why > > fwcontrol -u 0 -f 0 > fwcontrol -u 0 -r > > doesn't force the VIA into non-CYCLEMASTER mode the way > it (with -u 1) works for NEC? PR: kern/113785 VIA 6307, reported as: fwohci0: port 0xa800-0xa87f mem 0xfdffe000-0xfdffe7ff irq 18 at device 6.0 on pci1 AFAIK, the difference between 6306 and 6307 is the number of ports. Currently running FreeBSD 7.1 amd64. From sean.bruno at dsl-only.net Tue Nov 17 18:05:13 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Tue Nov 17 18:05:19 2009 Subject: VIA firewire controller and "non CYCLEMASTER mode" In-Reply-To: <200911162013.UAA01961@sopwith.solgatos.com> References: <200911162013.UAA01961@sopwith.solgatos.com> Message-ID: <1258481112.2706.40.camel@Lappy> On Mon, 2009-11-16 at 12:13 -0800, Dieter wrote: > It has been over a year, time to ask again: > > > If we assume that I need to get the VIA into non-CYCLEMASTER mode, > > (since that worked with the NEC), any ideas why > > > > fwcontrol -u 0 -f 0 > > fwcontrol -u 0 -r > > > > doesn't force the VIA into non-CYCLEMASTER mode the way > > it (with -u 1) works for NEC? > > PR: kern/113785 > > VIA 6307, reported as: > fwohci0: port 0xa800-0xa87f mem 0xfdffe000-0xfdffe7ff irq 18 at device 6.0 on pci1 > AFAIK, the difference between 6306 and 6307 is the number of ports. > > Currently running FreeBSD 7.1 amd64. Some day. *sigh* ... Sean From bugmaster at FreeBSD.org Mon Nov 23 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 23 11:07:54 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200911231106.nANB6p8D070100@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/139549 firewire [firewire] reconnecting a firewire disk does not cause o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 9 problems total.