I think its because of this, the Adafruit Python GPIO library broke. Is
there anyway to fix this? I fixed the I2C probably by changing the python
file, but unsure how for the SPI.
On Friday, March 21, 2014 11:41:06 AM UTC-5, David wrote:
Robert,
It appears that the GPIO label
Robert,
It appears that the GPIO label numbering scheme has been changed
from the device tree overlay's 1 to n+1, to the more con-formant 0 to
n; I fell into this trap :-[ . I will send you my consolidated patch
directly, once I had time to check it out further.
Sorry for the
Robert,
It looks like I spoke too soon. Although my device tree appears to
get loaded and my driver entry point is called with correct parameters,
the pinmux does not appear to get set up correctly. Where do I look in
3.13 kernel based systems to debug the pinmux settings?
Best regards,
Hey guys, I am trying to decide whether to stay on the 3.8 kernel or move
to 3.13 myself... The reason is that my usb wifi dongle does not work in
3.8 but it does in 3.12+. I am fairly new and just became familiar with
getting things to work using the device tree overlays and the cape
Just a suggestion. If the dtb for the cape does not exist or is
corrupted, could the device tree default to the base, for example
am335x-boneblack.dtb?
Dave.
On 03/05/2014 08:07 PM, Robert Nelson wrote:
On Wed, Mar 5, 2014 at 7:01 PM, David Lambert d...@lambsys.com wrote:
On 03/05/2014
On Thu, Mar 6, 2014 at 3:03 PM, David Lambert d...@lambsys.com wrote:
Just a suggestion. If the dtb for the cape does not exist or is corrupted,
could the device tree default to the base, for example am335x-boneblack.dtb?
You read my mind, there is a new file test function, i'd like to
backport
On 02/12/2014 12:56 PM, Robert Nelson wrote:
The path i'm going to start heading for v3.13.x/v3.14.x is just to do
separate major cape dtb's..
So in u-boot: fdtbase=am335x-bone or am335x-boneblack
cape=xzy (defined in uEnv.txt (lcd4-a1/etc))
Then it'll just load:
$fdtbase-$cape.dtb
on
On Wed, Mar 5, 2014 at 6:36 PM, David Lambert d...@lambsys.com wrote:
On 02/12/2014 12:56 PM, Robert Nelson wrote:
The path i'm going to start heading for v3.13.x/v3.14.x is just to do
separate major cape dtb's..
So in u-boot: fdtbase=am335x-bone or am335x-boneblack
cape=xzy (defined in
On 03/05/2014 06:52 PM, Robert Nelson wrote:
I just fixed this last friday, the 'cape' variable was used in the
wrong spot in u-boot so it never got used..
cd /opt/scripts/
git pull
./tools/update_bootloader.sh
I am confused, where is this script? I have searched netinstall and
linux-dev
On Wed, Mar 5, 2014 at 7:01 PM, David Lambert d...@lambsys.com wrote:
On 03/05/2014 06:52 PM, Robert Nelson wrote:
I just fixed this last friday, the 'cape' variable was used in the
wrong spot in u-boot so it never got used..
cd /opt/scripts/
git pull
./tools/update_bootloader.sh
I am
On 03/05/2014 08:07 PM, Robert Nelson wrote:
yeah, that's on my todo list, I need to add it to the netinstall by default.
sudo mkdir -p /opt/scripts/
sudo chown -R (user):(user) /opt/scripts
git clone git://github.com/RobertCNelson/boot-scripts /opt/scripts
It's a git repo where i'm stashing
Any updates on this?
On 02/12/2014 12:56 PM, Robert Nelson wrote:
c) Any other pointers?
I might have some free time this weekend..
The path i'm going to start heading for v3.13.x/v3.14.x is just to do
separate major cape dtb's..
So in u-boot: fdtbase=am335x-bone or am335x-boneblack
On Tue, Feb 25, 2014 at 11:32 AM, David Lambert d...@lambsys.com wrote:
Any updates on this?
Here's, just phase one to test the idea.
https://github.com/RobertCNelson/linux-dev/commit/685b182ca956dcd8396ca69af5c678c43a102d03
I'm heading out of the office in a little bit for the rest of day.
I am contemplating moving from 3.8.x to 3.13.x kernels due to the
apparent improvement in USB support. I am confused, however, as to the
state of device trees/overlays and their relationship with capes.
It appears to me that 3.8.x kernels use device tree overlays managed by
an internal kernel
On Wed, Feb 12, 2014 at 12:32 PM, David Lambert d...@lambsys.com wrote:
I am contemplating moving from 3.8.x to 3.13.x kernels due to the apparent
improvement in USB support. I am confused, however, as to the state of
device trees/overlays and their relationship with capes.
It appears to me
From: Robert Nelson robertcnel...@gmail.com
Reply-To: beagleboard@googlegroups.com
Date: Wednesday, February 12, 2014 at 10:56 AM
To: Beagle Board beagleboard@googlegroups.com
Subject: Re: [beagleboard] Kernel/device tree road-map for the BBB
On Wed, Feb 12, 2014 at 12:32 PM, David
Thanks Robert. That sounds like a good plan.
Dave.
On 02/12/2014 12:56 PM, Robert Nelson wrote:
On Wed, Feb 12, 2014 at 12:32 PM, David Lambert d...@lambsys.com
mailto:d...@lambsys.com wrote:
I am contemplating moving from 3.8.x to 3.13.x kernels due to the
apparent improvement
17 matches
Mail list logo
