On Wed, Apr 23, 2014 at 11:48 PM, Frank Rowand wrote:
> On 4/23/2014 4:54 AM, Grant Likely wrote:
>> On Tue, 22 Apr 2014 20:20:44 -0700, Greg Kroah-Hartman
>> wrote:
>>> On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
Create some infrastructure to aid trouble shooting device
On Wed, Apr 23, 2014 at 11:48 PM, Frank Rowand frowand.l...@gmail.com wrote:
On 4/23/2014 4:54 AM, Grant Likely wrote:
On Tue, 22 Apr 2014 20:20:44 -0700, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
Create some
On Wed, Apr 23, 2014 at 03:45:11PM -0700, Frank Rowand wrote:
> >> 3) To find list of device tree nodes with a bound driver:
> >>
> >> # output is: driver_name node_full_path
> >> #
> >> cd /proc/device-tree
> >> for k in `find . -name %driver_name` ; do
> >> echo `cat ${k}` `echo
On 4/23/2014 4:54 AM, Grant Likely wrote:
> On Tue, 22 Apr 2014 20:20:44 -0700, Greg Kroah-Hartman
> wrote:
>> On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
>>> Create some infrastructure to aid trouble shooting device tree related
>>> boot issues.
>>>
>>> Add a %driver_name file
On 4/22/2014 8:20 PM, Greg Kroah-Hartman wrote:
> On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
>> Create some infrastructure to aid trouble shooting device tree related
>> boot issues.
>>
>> Add a %driver_name file to each device tree node sysfs directory which has
>> had
>> a
On Tue, 22 Apr 2014 20:20:44 -0700, Greg Kroah-Hartman
wrote:
> On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
> > Create some infrastructure to aid trouble shooting device tree related
> > boot issues.
> >
> > Add a %driver_name file to each device tree node sysfs directory
On 4/22/2014 8:20 PM, Greg Kroah-Hartman wrote:
On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
Create some infrastructure to aid trouble shooting device tree related
boot issues.
Add a %driver_name file to each device tree node sysfs directory which has
had
a driver bound to
On 4/23/2014 4:54 AM, Grant Likely wrote:
On Tue, 22 Apr 2014 20:20:44 -0700, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
Create some infrastructure to aid trouble shooting device tree related
boot issues.
Add a
On Wed, Apr 23, 2014 at 03:45:11PM -0700, Frank Rowand wrote:
3) To find list of device tree nodes with a bound driver:
# output is: driver_name node_full_path
#
cd /proc/device-tree
for k in `find . -name %driver_name` ; do
echo `cat ${k}` `echo ${k} | sed -e
On Tue, 22 Apr 2014 20:20:44 -0700, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
Create some infrastructure to aid trouble shooting device tree related
boot issues.
Add a %driver_name file to each device tree node
On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
> Create some infrastructure to aid trouble shooting device tree related
> boot issues.
>
> Add a %driver_name file to each device tree node sysfs directory which has had
> a driver bound to it. This allows detecting device tree nodes
On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote:
Create some infrastructure to aid trouble shooting device tree related
boot issues.
Add a %driver_name file to each device tree node sysfs directory which has had
a driver bound to it. This allows detecting device tree nodes
12 matches
Mail list logo
