Date: Mon, 23 Aug 2004 15:25:25 -0700 From: George Hartzell <hartzell@kestrel.alerce.com> To: freebsd-current@freebsd.org Subject: firewire bug, or just drop it [was Re: Help making sense of ] Message-ID: <16682.28373.980795.545928@rosebud.alerce.com> In-Reply-To: <20040823101023.R4628@carver.gumbysoft.com> References: <16679.59263.287454.325068@rosebud.alerce.com> <20040822193851.K94593@carver.gumbysoft.com> <16681.26689.215660.854423@rosebud.alerce.com> <20040823101023.R4628@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White writes: > On Sun, 22 Aug 2004, George Hartzell wrote: > > [...] > > I figured out how to ask fwcontrol to tell me more about the device > > inside the enclosure, and discovered that it's a Prolific PL-3507. A > > little googling about suggests that it's a well known PITA device, e.g. > > > > http://forum.rpc1.org/viewtopic.php?t=25140&postdays=0&postorder=asc&&start=0&sid=0a359d410cfd87df72f2543365922421 > > > > So, I'm left to decide whether to muck with the firmware or just chuck > > it..... > > I'd give up now. :) > [...] [background: I've been unsuccessfully messing about with a firewire enclosure and 5.2.1 release (and 6.0), it turns out it uses a chip that's known to be problematic] Are the folks that support the firewire stuff interested in supporting spastic hardware like this? I could file a pr for it, but I'm not sure it's a bug. I haven't encountered quite this situation before and don't know what the Right Thing To Do is. I could make the hardware available if it'd help tighten up the subsystem. g.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16682.28373.980795.545928>