On Saturday 05 March 2005 17:06, Lee Revell wrote: >On Sat, 2005-03-05 at 16:49 -0500, Gene Heskett wrote: >> What he said! Perfectly good patches, which fix real problems >> would appear to be sitting in testing/broken_out till bit rot or >> ???. >> >> If you want a testers testimony, I'm running the >> bk-ieee1394.patch, and all I can say at this point is that it Just >> Works(TM). I have NDI how it got a yesterdays Mar 4) date in the >> directory listing there though, I've had it a bit longer than that >> by 2-3 days as my copy shows a Mar 1 date. I first got it via svn >> fetch at linux-ieee1394.org or some such in January. >> >> Fixes for real problems that fix real problems should somehow get >> a faster track into final. The current firewire in the kernel as >> of 2.6.11 is still badly borked. > >Driver updates are a hard problem. Nothing annoys users more than >unsupported hardware. But if you aggressively add support for new >devices you can break things that have worked for ages. > >A change that makes your hardware work may break someone else's. > There is no such thing as an obviously correct patch when you are > flipping bits in the hardware. You can never eliminate 100% of > driver regressions, all you can do is minimize the impact by > getting release candidates tested on the widest possible range of > hardware. > >Lee
True up to a certain extent, Lee. I did not own any firewire stuff except for a 6 year old firewire card I didn't have anything to plug into, a TI of some sort that supposedly needed the ti-linx driver, until I bought this camera. That card quickly proved to be borked per comments made on the linux-firewire list, and got replaced with a $25 belkin card from wallyworld. One buys whats available at your friendly local wallyworld as a first pass at fixing things. That worked great when it felt like it, which wasn't often. Now, with this patch, it Just Works(TM). My point is that if it doesn't get into mainline, how are you going to know it it breaks something that formerly worked? In my case, it certainly fixed something that didn't work, and didn't break anything that I know of *yet*. I have quite a managerie of accessories hanging off of the various ports, mostly usb on this box, and I have a regular tour of them I make when I reboot to a newer kernel, so if something breaks sane, or printing, networking, x10, what have you, I usually know about it within 30 minutes of the reboot. Frankly, I was surprised that this elcheapo belkin card worked so good! Their bigger ups's, and this card seem to be the exception to the mainline and very prominent story of all their broken KVM switches. A pleasant surprise in light of my reticence to even put fingerprints on many of the belkin boxes on the shelf at Staples et all. However, that doesn't address the fact that the patch I grabbed, dated Mar 1, is apparently older than the one in testing/broken_out dated Mar 4. Both are 265824 bytes long however, so I'm going to go with the theory that someone rebuilt the directory on kernel.org. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
