From: Gunther Mayer <gunther.mayer@gmx.net>
To: Andre Hedrick <andre@linuxdiskcert.org>
Cc: Martin Dalecki <dalecki@evision-ventures.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.6 IDE oops with i810 chipset
Date: Fri, 08 Mar 2002 17:53:02 +0100 [thread overview]
Message-ID: <3C88EC6E.C59BC167@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10203080831480.504-100000@master.linux-ide.org>
Andre Hedrick wrote:
> On Fri, 8 Mar 2002, Martin Dalecki wrote:
>
> > Luigi Genoni wrote:
> > > Due to a lack of time i tried just 2.5.5, which worked very well.
> > > I get the oops while initializing the IDE controller, just after
> > >
> > > hdc: LTN485, ATAPI CD/DVD-ROM drive
> > >
> > > and before the expected:
> > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > >
> >
> > OK thank you very much this helps. I will actually have to fake the
> > detection on my system to think it's the same as yours...
> > One thing for sure: it's not dircetly inside the
> > PCI host initialization, so I wonder why this problem
> > doesn't occur to more people.
>
> You will soon learn about the way ATAPI removable media violate the rules
> of how the maintain their status and signal lines. However you already
> knew this information as I am wasting electrons
Can you get more specific ?
Do you mean
a) Some ATAPI devices violate the "ATA/ATAPI-4" NCITS 317-1998 standard (or
a newer version),
And your driver contained workarounds for these buggy devices? (And
Martins driver doesn't contain these.)
b) Your driver conforms to the standard, and Martin's driver does not?
next prev parent reply other threads:[~2002-03-08 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 14:20 2.5.6 IDE oops with i810 chipset Luigi Genoni
2002-03-08 14:44 ` Luigi Genoni
2002-03-08 14:47 ` Martin Dalecki
2002-03-08 15:54 ` Luigi Genoni
2002-03-08 16:17 ` Martin Dalecki
2002-03-08 16:34 ` Andre Hedrick
2002-03-08 16:53 ` Gunther Mayer [this message]
2002-03-08 17:07 ` Andre Hedrick
2002-03-09 12:40 ` Martin Dalecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C88EC6E.C59BC167@gmx.net \
--to=gunther.mayer@gmx.net \
--cc=andre@linuxdiskcert.org \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox