Partly, it is for my own driver. I was going to just piggy-back on the
existing mechanism.
In addition, I am working with the MPC8313E-RDB BSP from Freescale and
discovered that in their release for the rev. C board, they changed the
RTC driver from 10,135 to 254,0 but didn't change device_table.txt so
/dev/rtc wouldn't work. I have to now admit that the proper thing to do
is to fix the driver, not the device_table.
So I guess the bottom line is to dynamically add new devices instead of
adding them to device_table.txt. Makes sense, though it would be nice
to have dev merge in a private device table from the platform directory.
Thanks
----- Original Message ----- From: "Stuart Hughes" <address@hidden>
To: "Ted Marshall" <address@hidden>
Cc: <address@hidden>
Sent: Thursday, July 30, 2009 10:09 AM
Subject: Re: [Ltib] Question on adding device nodes
Hi Ted,
What do you want to change? the device node values are fixed and
global to all kernels. You should not need to change this file unless
something is missing. The idea is this is common to all BSPs.
If you have your own driver then you need to dynamically create a node.
Regards, Stuart
Ted Marshall wrote:
Per http://www.bitshrine.org/autodocs/LtibFaq.html#ref_106,
ltib/bin/device_table.txt is used by package "dev" to create the
device nodes in the root fs. What is the best way to make changes
which are specific to one build? It seems unreasonable to have the
specific kernel package overwrite this "global" file.
Is there a way to make the dev package read a different file, perhaps
one in ltib/config/platform?
Suggestions?
Thanks,
/Ted Marshall