On Fri, Mar 25, 2005 at 09:03:57PM +, Russell King wrote:
> > It would be trivial to treat them both as foobar0 and have the
> > registration succeed for whoever gets it first, but I could see that this
> > would be problematic in the serial8250 case. On the other hand, this is
> > then
On Fri, Mar 25, 2005 at 10:56:03PM +0200, Paul Mundt wrote:
> On Fri, Mar 25, 2005 at 08:25:08PM +, Russell King wrote:
> > Eh? How do you end up with "/sys/devices/platform/foobar0.0" for the
> > former case? It has an ID of "-1", and not zero. Your idea doesn't
> > make any sense.
> >
>
On Fri, Mar 25, 2005 at 08:25:08PM +, Russell King wrote:
> Eh? How do you end up with "/sys/devices/platform/foobar0.0" for the
> former case? It has an ID of "-1", and not zero. Your idea doesn't
> make any sense.
>
Yes, I missed the -1 part, so Kyle is correct.
It would be trivial to
On Fri, Mar 25, 2005 at 09:58:26PM +0200, Paul Mundt wrote:
> On Fri, Mar 25, 2005 at 02:38:22PM -0500, Kyle Moffett wrote:
> > So how would you tell the difference between the following?
> > device = "foobar0"
> > id = -1
> > path = "/sys/devices/platform/foobar0"
> > versus
> >
On Mar 25, 2005, at 14:58, Paul Mundt wrote:
On Fri, Mar 25, 2005 at 02:38:22PM -0500, Kyle Moffett wrote:
So how would you tell the difference between the following?
device = "foobar0"
id = -1
path = "/sys/devices/platform/foobar0"
versus
device = "foobar"
On Fri, Mar 25, 2005 at 02:38:22PM -0500, Kyle Moffett wrote:
> So how would you tell the difference between the following?
> device = "foobar0"
> id = -1
> path = "/sys/devices/platform/foobar0"
> versus
> device = "foobar"
> id = 0
> path =
On Mar 25, 2005, at 13:35, Paul Mundt wrote:
Anything that expects that it can open a
/sys/devices/platform/
path. I have a few applications like this, I have no reason to doubt
that
others do too. I don't see any reason to go out of the way to break
this
convention if the end of the device
On Fri, Mar 25, 2005 at 10:10:14AM -0800, Greg KH wrote:
> > This might make sense for devices that end in numbers, but does it really
> > make sense for devices that don't?
>
> Then fix those drivers to not put the number in there if they don't have
> one :)
>
But they do have non -1 ids, the
On Fri, Mar 25, 2005 at 08:01:36PM +0200, Paul Mundt wrote:
> On Wed, Mar 09, 2005 at 04:34:39PM -0800, Greg KH wrote:
> > [PATCH] driver core: Separate platform device name from platform device
> > number
> >
> > Separate platform device name from platform device
On Wed, Mar 09, 2005 at 04:34:39PM -0800, Greg KH wrote:
> [PATCH] driver core: Separate platform device name from platform device number
>
> Separate platform device name from platform device number such that
> names ending with numbers aren't confusing.
>
This might make se
On Wed, Mar 09, 2005 at 04:34:39PM -0800, Greg KH wrote:
[PATCH] driver core: Separate platform device name from platform device number
Separate platform device name from platform device number such that
names ending with numbers aren't confusing.
This might make sense for devices that end
On Fri, Mar 25, 2005 at 08:01:36PM +0200, Paul Mundt wrote:
On Wed, Mar 09, 2005 at 04:34:39PM -0800, Greg KH wrote:
[PATCH] driver core: Separate platform device name from platform device
number
Separate platform device name from platform device number such that
names ending
On Fri, Mar 25, 2005 at 10:10:14AM -0800, Greg KH wrote:
This might make sense for devices that end in numbers, but does it really
make sense for devices that don't?
Then fix those drivers to not put the number in there if they don't have
one :)
But they do have non -1 ids, the device
On Mar 25, 2005, at 13:35, Paul Mundt wrote:
Anything that expects that it can open a
/sys/devices/platform/deviceid
path. I have a few applications like this, I have no reason to doubt
that
others do too. I don't see any reason to go out of the way to break
this
convention if the end of the
On Fri, Mar 25, 2005 at 02:38:22PM -0500, Kyle Moffett wrote:
So how would you tell the difference between the following?
device = foobar0
id = -1
path = /sys/devices/platform/foobar0
versus
device = foobar
id = 0
path = /sys/devices/platform/foobar0
On Mar 25, 2005, at 14:58, Paul Mundt wrote:
On Fri, Mar 25, 2005 at 02:38:22PM -0500, Kyle Moffett wrote:
So how would you tell the difference between the following?
device = foobar0
id = -1
path = /sys/devices/platform/foobar0
versus
device = foobar
id = 0
On Fri, Mar 25, 2005 at 09:58:26PM +0200, Paul Mundt wrote:
On Fri, Mar 25, 2005 at 02:38:22PM -0500, Kyle Moffett wrote:
So how would you tell the difference between the following?
device = foobar0
id = -1
path = /sys/devices/platform/foobar0
versus
device = foobar
On Fri, Mar 25, 2005 at 08:25:08PM +, Russell King wrote:
Eh? How do you end up with /sys/devices/platform/foobar0.0 for the
former case? It has an ID of -1, and not zero. Your idea doesn't
make any sense.
Yes, I missed the -1 part, so Kyle is correct.
It would be trivial to treat
On Fri, Mar 25, 2005 at 10:56:03PM +0200, Paul Mundt wrote:
On Fri, Mar 25, 2005 at 08:25:08PM +, Russell King wrote:
Eh? How do you end up with /sys/devices/platform/foobar0.0 for the
former case? It has an ID of -1, and not zero. Your idea doesn't
make any sense.
Yes, I missed
On Fri, Mar 25, 2005 at 09:03:57PM +, Russell King wrote:
It would be trivial to treat them both as foobar0 and have the
registration succeed for whoever gets it first, but I could see that this
would be problematic in the serial8250 case. On the other hand, this is
then serial8250's
ChangeSet 1.2038, 2005/03/09 09:32:19-08:00, [EMAIL PROTECTED]
[PATCH] driver core: Separate platform device name from platform device number
Separate platform device name from platform device number such that
names ending with numbers aren't confusing.
Signed-off-by: Russell King <[EM
ChangeSet 1.2038, 2005/03/09 09:32:19-08:00, [EMAIL PROTECTED]
[PATCH] driver core: Separate platform device name from platform device number
Separate platform device name from platform device number such that
names ending with numbers aren't confusing.
Signed-off-by: Russell King [EMAIL
22 matches
Mail list logo