From: Alan Cox <alan@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alan Cox <alan@redhat.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Fix ide probe double detection
Date: Thu, 29 Jul 2004 09:39:03 -0400 [thread overview]
Message-ID: <20040729133903.GA12406@devserv.devel.redhat.com> (raw)
In-Reply-To: <1091071364.13625.37.camel@gaston>
On Thu, Jul 29, 2004 at 01:22:44PM +1000, Benjamin Herrenschmidt wrote:
> I don't like relying on drive->id and serial_no, but that may just be
> paranoia...
I've seen no evidence to indicate anyone has duplicate serial numbers
even with CF cards so I think its fine. The problem with playing with
registers and seeing if they stick is that on the newer cards the
register bank you are programming is sometimes a fifo ahead of the real
drive.
Alan
next prev parent reply other threads:[~2004-07-29 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 22:46 PATCH: Fix ide probe double detection Alan Cox
2004-07-29 3:22 ` Benjamin Herrenschmidt
2004-07-29 13:39 ` Alan Cox [this message]
2004-07-29 15:56 ` Doug Maxey
2004-07-29 16:02 ` Alan Cox
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=20040729133903.GA12406@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--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