All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Naming devices
Date: Mon, 19 May 2003 13:40:31 +1000	[thread overview]
Message-ID: <20030519034031.GI8994@krispykreme> (raw)
In-Reply-To: <20030518233634.C4224@flint.arm.linux.org.uk>

 
> Isn't this what dev->bus_id in the device structure is supposed to be?
> (which is supposed to be a unique bus ID on a particular bus type, in
> the pci case, a PCI device.)

We could use that, although for ppc64 Id like to increase its size and
stash the physical location in there as well.

> Now that the point has been raised, it seems pretty obvious that
> initialisation failures should report the BUS ID of the failing card,
> not the logical name assigned by the system to that device which could
> change.  Once the card is up and running, using the logical name becomes
> meaningful - it's the identifier which user space uses to reference the
> device.

Sounds good to me.

Anton

  reply	other threads:[~2003-05-19  3:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 21:33 Naming devices Anton Blanchard
2003-05-18 22:36 ` Russell King
2003-05-19  3:40   ` Anton Blanchard [this message]
2003-05-19  1:22 ` Daniel Stekloff
2003-05-19  1:48   ` David S. Miller

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=20030519034031.GI8994@krispykreme \
    --to=anton@samba.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 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.