From: Gleb Natapov <gleb@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Hannes Reinecke <hare@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH] EDD: Check for correct EDD 3.0 length
Date: Tue, 15 May 2012 18:29:42 +0300 [thread overview]
Message-ID: <20120515152942.GH6948@redhat.com> (raw)
In-Reply-To: <20120515162226.1b9a7496@pyramind.ukuu.org.uk>
On Tue, May 15, 2012 at 04:22:26PM +0100, Alan Cox wrote:
> On Tue, 15 May 2012 17:53:16 +0300
> Gleb Natapov <gleb@redhat.com> wrote:
>
> > On Tue, May 15, 2012 at 03:52:06PM +0100, Alan Cox wrote:
> > > > It is easy to be confused since there are two EDD 3 specs. First is from
> > > > Phoenix BIOS (linked at the first mail of the thread) and it does not have
> > > > enough info even for ATA. You can't tell primary ATA controller from secondary.
> > >
> > > Yes you can - it's defined by the PCI specification for compatibility
> > How? ATA device path has only Master/Slave. Interface path has only
> > bus/slot/function. So given all that in int13_80 how do I know if this
> > is primary or secondary controller?
>
> For compatibility mode by the I/O port address.
>
Hmm, will work if standard I/O addresses are used for master/slave, but
I do not see this information be exposed via /sys by EDD. So how can I
do it from OS installer with current kernel or kernel with reverted
patch?
> For native mode most controllers pretend to be two devfns for exactly
> this reason, and report one on each. Some non-MMIO devices don't and you
> can tell them apart by looking at the addresses given in DPTE as well.
>
> Simples..
>
> Alan
--
Gleb.
next prev parent reply other threads:[~2012-05-15 15:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 11:04 [PATCH] EDD: Check for correct EDD 3.0 length Hannes Reinecke
2012-05-15 11:12 ` Gleb Natapov
2012-05-15 11:20 ` Hannes Reinecke
2012-05-15 11:59 ` Gleb Natapov
2012-05-15 12:53 ` Gleb Natapov
2012-05-15 13:49 ` Alan Cox
2012-05-15 14:12 ` Gleb Natapov
2012-05-15 14:18 ` Alan Cox
2012-05-15 14:21 ` Gleb Natapov
2012-05-15 14:36 ` Alan Cox
2012-05-15 14:48 ` Gleb Natapov
2012-05-15 14:54 ` Alan Cox
2012-05-15 15:00 ` Gleb Natapov
2012-05-15 14:00 ` Alan Cox
2012-05-15 14:36 ` Gleb Natapov
2012-05-15 14:52 ` Alan Cox
2012-05-15 14:53 ` Gleb Natapov
2012-05-15 15:22 ` Alan Cox
2012-05-15 15:29 ` Gleb Natapov [this message]
2012-05-15 15:41 ` Alan Cox
2012-05-15 15:53 ` Gleb Natapov
2012-05-15 15:14 ` Alan Cox
2012-05-15 15:31 ` Alan Cox
2012-05-15 15:46 ` Gleb Natapov
2012-05-15 17:17 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2012-05-16 6:51 Hannes Reinecke
2012-05-16 8:28 ` Gleb Natapov
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=20120515152942.GH6948@redhat.com \
--to=gleb@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hare@suse.de \
--cc=hpa@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.