From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: PowerPC dev list <Linuxppc-dev@ozlabs.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Markus Rechberger <markus.rechberger@amd.com>
Subject: Re: Fix Firmware class name collision
Date: Tue, 04 Dec 2007 19:28:00 -0600 [thread overview]
Message-ID: <4755FEA0.1050005@freescale.com> (raw)
In-Reply-To: <4755E835.6070704@freescale.com>
Scott Wood wrote:
> The physical address certainly is useful when you have more than one
> device of the same name.
What I meant was that the physical address isn't helpful by itself.
> So then you'd get "firmware-ucc.e01024". What if there's another ucc at
> e0102480? For devices with longer names, you'd have even less
> precision in the address.
Maybe we need to consider a more sophisticated algorithm, one that guarantees
that the device name in its entirety is preserved? Either that, or replace
the physical address with something shorter, like the offset to the root node
only? That way, ucc.e0102400 because just ucc.2400.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-12-05 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 23:45 Fix Firmware class name collision Timur Tabi
2007-12-04 23:52 ` Scott Wood
2007-12-05 1:28 ` Timur Tabi [this message]
2007-12-14 22:40 ` Greg KH
2007-12-14 22:46 ` Timur Tabi
2007-12-15 6:14 ` Benjamin Herrenschmidt
2007-12-15 6:39 ` Greg KH
2007-12-15 15:46 ` Kay Sievers
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=4755FEA0.1050005@freescale.com \
--to=timur@freescale.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=gregkh@suse.de \
--cc=markus.rechberger@amd.com \
--cc=scottwood@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).