[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <37458316-F50D-4E4A-A59B-01CB8A6FC108@kernel.crashing.org>
Date: Wed, 10 Aug 2011 12:26:17 -0500
From: Kumar Gala <galak@...nel.crashing.org>
To: Robin Holt <holt@....com>
Cc: Wood Scott-B07421 <B07421@...escale.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
U Bhaskar-B22300 <B22300@...escale.com>,
"socketcan-core@...ts.berlios.de" <socketcan-core@...ts.berlios.de>,
PPC list <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH v10 5/5] [powerpc] Fix up fsl-flexcan device tree binding.
>>>>>>> So the node names should be
>>>>>>> can@...00 {
>>>>>>> can@...00 {
>>>>>>> correct?
>>>>>>>
>>>>>> [Bhaskar] As there are two CAN controllers on P1010,So won't it be better
>>>>>> to distinguish it by can0 and can1 instead by simple "can" ?
>>>>>
>>>>> It looks like the way to do that is to assign a label to those devices
>>>>> and then associate the label with an alias. I have no idea how that
>>>>> works under the hood, but it is the way other files are set up. Take a
>>>>> look at arch/powerpc/boot/dts/bamboo.dts for how they define the serial
>>>>> interfaces.
>>>>>
>>>>> Grant or Wolfgang, is that the right way to handle the concern about
>>>>> names or does it have no practical effect with the Linux kernel?
>>>>
>>>> It has not effect. The label is just if you need to reference it via some other means.
>>>
>>> Does the alias have an effect?
>>
>> nope
>
> Then how does the device number get associated with a particular device
What do you mean by device number?
> and how is user-space ensured a consistent namespace?
that is left to udev rules.
- k--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists