I still want to be able to understand how to enable the ports and use one wire
in the newer kernels. I can see the one wire driver being loaded on startup.
But I cannot see /sys/devices/w1_devices
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because
So, I'm finding the Really Simple Cape Manager anything but simple...
I made a Java DTO library that would use a JSON file
(https://github.com/DougEdey/SB_Elsinore_Server/blob/master/extras/beaglebone.json)
to create Device Tree Overlays that could be applied easily.
This created files that
On Thu, Nov 20, 2014 at 8:55 PM, Doug Edey doug.e...@gmail.com wrote:
So, I'm finding the Really Simple Cape Manager anything but simple...
I made a Java DTO library that would use a JSON file
(https://github.com/DougEdey/SB_Elsinore_Server/blob/master/extras/beaglebone.json)
to create Device
OK, I'm still unclear as to how my old dts for one wire:
/*
* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free
On Thu, Nov 20, 2014 at 9:16 PM, Doug Edey doug.e...@gmail.com wrote:
OK, I'm still unclear as to how my old dts for one wire:
/*
* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
*
* This program is free software; you can redistribute it and/or modify
* it under the
I ran that and it seemed to compile and install OK.
But dmesg shows an error:
[ 20.170288] =
[ 20.175949] [ INFO: possible recursive locking detected ]
[ 20.181616] 3.14.22-ti-r31 #1 Tainted: G O
[ 20.186820]
On Thu, Nov 20, 2014 at 9:54 PM, Doug Edey doug.e...@gmail.com wrote:
I ran that and it seemed to compile and install OK.
But dmesg shows an error:
[ 20.170288] =
[ 20.175949] [ INFO: possible recursive locking detected ]
[ 20.181616]
The DTB doesn't match the hardware, it matches the kernel? That seems
odd...
I ran those. commands, uEnv still points at am335-boneblack.dtb, but I
don;t see any one wire devices, even though there is one connected in the
same configuration as the old kernel 3.8 that used the previous DTB
On Thu, Nov 20, 2014 at 10:25 PM, Doug Edey doug.e...@gmail.com wrote:
The DTB doesn't match the hardware, it matches the kernel? That seems
odd...
I ran those. commands, uEnv still points at am335-boneblack.dtb, but I don;t
see any one wire devices, even though there is one connected in
Then just:
sudo apt-get update
sudo apt-get install linux-image-3.8.13-bone67
sudo reboot
Running
What was the reason for the change away from capemgr? capemgr seemed to
work
Search the list, it's been explained too often.
Surely, as a fellow software dev, if you have to
Surely, as a fellow software dev, if you have to explain yourself a lot,
there's an issue (I've worked on a lot of massive projects down to the low
level, JVM - network management product for ISPs/larger)
Simply, what was developed for v3.8.x was out-right rejected by
mainline. The main
On Thursday, November 20, 2014 11:32:13 PM UTC-5, RobertCNelson wrote:
On Thu, Nov 20, 2014 at 10:25 PM, Doug Edey doug...@gmail.com
javascript: wrote:
The DTB doesn't match the hardware, it matches the kernel? That
seems
odd...
I ran those. commands, uEnv still points at
12 matches
Mail list logo
