Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
- Date: Wed, 02 Jul 2008 11:35:22 +0200
Maciej W. Rozycki wrote:
On Mon, 30 Jun 2008, Rafael J. Wysocki wrote:
Well, there are lots of pieces of hardware that are not up to the
specifications, more or less, and I don't think that's a good enough reason
for us to refuse to support them. The same applies to BIOSes IMO.
Refusing to support broken hardware would provide some incentive to
manufacturers to improve it, because people would rather not buy
unsupported pieces of junk.
For most consumer level hardware the vendors generally don't
really care if Linux runs on it or not.
Also they very rarely fix anything after release anyways because
they don't make enough money on it.
For server hardware that is different (vendors care about Linux,
but typically not about mainline, but about given RHEL/SLES releases),
but even there we generally try to work around BIOS bugs
(at least as long as it is possible)
because it tends to be quite difficult logistically to require
a BIOS update. In the end it just hurts the user.
I realise that may be impractical though
It is.
we would get the blame anyway, because "it runs the other OS just fine."
That is exactly what happens.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
- From: Maciej W. Rozycki
- Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
- Prev by Date: Re: [PATCH] drivers/edac: i5100_edac cleanup
- Next by Date: RE: [RFC] How to handle the rules engine for cgroups
- Previous by thread: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
- Next by thread: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
- Index(es):
Relevant Pages
|
