On Mon, 2006-12-18 at 14:48 +0100, Krzysztof Halasa wrote:
> Arjan van de Ven <[EMAIL PROTECTED]> writes:
>
> > if a tree falls in a forest but there's nobody around to hear it, does
> > it make a sound?
> >
> > This sort of heisenbug questions aren't solved by "nobody hears it so
> > lets chop do
Arjan van de Ven <[EMAIL PROTECTED]> writes:
> if a tree falls in a forest but there's nobody around to hear it, does
> it make a sound?
>
> This sort of heisenbug questions aren't solved by "nobody hears it so
> lets chop down the forest to make houses out of the wood" answers...
Does that mean
On Sun, 2006-12-17 at 22:18 +0100, Krzysztof Halasa wrote:
> James Bottomley <[EMAIL PROTECTED]> writes:
>
> > One of the touted benefits of Linux is that we run on old hardware.
> > Unless the driver is demonstrably wrong (and they do become so as the
> > APIs evolve)
>
> Sure, I expect they do
James Bottomley <[EMAIL PROTECTED]> writes:
> One of the touted benefits of Linux is that we run on old hardware.
> Unless the driver is demonstrably wrong (and they do become so as the
> APIs evolve)
Sure, I expect they do - but nobody is able to check.
> The reverse (how do you know if someone
On Sun, 2006-12-17 at 21:03 +0100, Krzysztof Halasa wrote:
> James Bottomley <[EMAIL PROTECTED]> writes:
>
> > I really don't see a need to declare drivers obsolete unless they bitrot
> > to the point they're demonstrably useless and no-one wants to step up to
> > fix them, which is what the BROKE
James Bottomley <[EMAIL PROTECTED]> writes:
> I really don't see a need to declare drivers obsolete unless they bitrot
> to the point they're demonstrably useless and no-one wants to step up to
> fix them, which is what the BROKEN flag is for.
How do you know if the driver is broken? Especially i
On Fri, 2006-12-15 at 14:34 +0100, Krzysztof Halasa wrote:
> Adrian Bunk <[EMAIL PROTECTED]> writes:
>
> > There must have been a compile error that has since been fixed, but I
> > don't remember the details of this specific driver and I don't have
> > such old compile logs anymore.
>
> I wonde
Am Freitag, 15. Dezember 2006 14:34 schrieb Krzysztof Halasa:
> I find it really hard to believe there are still users of things like
> CDU-31A CDs, XT MFM disk controllers, or NCR5380 SCSI host adapters
> (especially the real ones, not DOMEX etc. clones bundled with scanner
> just ~ 10 years ago).
Adrian Bunk <[EMAIL PROTECTED]> writes:
> There must have been a compile error that has since been fixed, but I
> don't remember the details of this specific driver and I don't have
> such old compile logs anymore.
I wonder if we could gather some usage statistics, especially WRT
really old har
On Tue, Dec 12, 2006 at 05:31:14PM -0600, James Bottomley wrote:
> On Tue, 2006-12-12 at 17:22 +0100, Adrian Bunk wrote:
> > The SCSI_SEAGATE driver has:
> > - already been marked as BROKEN in 2.6.0 three years ago and
> > - is still marked as BROKEN.
> >
> > Drivers that had been marked as BROKEN
On Tue, 2006-12-12 at 17:22 +0100, Adrian Bunk wrote:
> The SCSI_SEAGATE driver has:
> - already been marked as BROKEN in 2.6.0 three years ago and
> - is still marked as BROKEN.
>
> Drivers that had been marked as BROKEN for such a long time seem to be
> unlikely to be revived in the forseeable f
The SCSI_SEAGATE driver has:
- already been marked as BROKEN in 2.6.0 three years ago and
- is still marked as BROKEN.
Drivers that had been marked as BROKEN for such a long time seem to be
unlikely to be revived in the forseeable future.
But if anyone wants to ever revive this driver, the code i
12 matches
Mail list logo
