On Mon, Oct 02, 2000 at 01:39:40PM -0500, Jeff Garzik wrote:
> Linus,
>
> Ug. Why do I feel like the IDE "driver" is code layered upon code
> layered upon code, through the ages, with nary a cleanup in between?
>
> My previous patch was a fix, but (brown paper bag time) standard IDE
> devices
No kidding, it is scheduled for a RAPE and BURN for a redesign for 2.5.
Until then do not make changes that cause problems with 'class' code ID's.
Cheers,
On Mon, 2 Oct 2000, Jeff Garzik wrote:
> Linus,
>
> Ug. Why do I feel like the IDE "driver" is code layered upon code
> layered upon code
> My previous patch was a fix, but (brown paper bag time) standard IDE
> devices no longer called chipset init. People either had no IDE, or
> were stuck in legacy mode. This fixes it.
This fixes the bootup oops with 2.4.0-test9-pre8 i reported
on lkml an hour or 2 ago.
b
<[EMAIL PROTECTED]>
<
Linus,
Ug. Why do I feel like the IDE "driver" is code layered upon code
layered upon code, through the ages, with nary a cleanup in between?
My previous patch was a fix, but (brown paper bag time) standard IDE
devices no longer called chipset init. People either had no IDE, or
were stuck in l
4 matches
Mail list logo
