Call for Angstrom and kernel contributions for next-generation BeagleBone

Jason, are you saying that 3.8 will be the kernel version for the new Image?

Yes.

If that is the case I have a few patches that I would like to submit! The
patches have been developed on Robert Nelsons kernel 3.8 patchset, so I'm
trying to determine what needs to be done to port them, hopefully very
little.

Please send a pull-request against
GitHub - beagleboard/kernel: Kernel for the beagleboard.org boards ASAP. There's actually less time
to close this than what I said earlier.

Robert has been pretty good at keeping his kernel aligned as far as I
understand, so your patches should apply fairly cleanly. Just note
that Koen and Panto are looking to close it up for release and might
push back.

Okay, I had to split the patch in two.. Koen and Panto might push back
on the big one, as it's touching quite a few subsections so close to
the image deadline..

They are here for the moment..
https://github.com/RobertCNelson/linux-dev/commit/f3672f650d06e8c0ab4da27da9a0ffde6ccd0b44

At the moment I'm actually trying to find some 'network bandwidth' so
i can re clone "kernel.git".. then I'll push a merge request so
everyone can review it for Elias..

Regards,

github seems to be having problems this morning. :wink:

Anyways: the merge request is up:

https://github.com/beagleboard/kernel/pull/34
Elias please review encase i missed something..

So far it builds, have not ran tested yet...

Regards,

Robert, I’m sorry, the patch does not work… Sorry to be causing problems this close to the finish line…
The actual firmware file was not caught by diff, so it was not added. Also a new cape had snuck in at spot number 10…

Attached is a patch that fixes it.

Also, I have found that reading from the ADC kill the Touch screen, so there is obviously a bug here. I’ll try to
fix it in a jiffy, but I’m afraid I cannot reccomend the current merge… Again super sorry… : (

fix-add-replicape-firmware-support.patch (6.65 KB)

Robert, I'm sorry, the patch does not work.. Sorry to be causing problems
this close to the finish line..
The actual firmware file was not caught by diff, so it was not added. Also a

I took care of this.. (missed the git add .)

new cape had snuck in at spot number 10..

Crap, didn't notice this.. and Koen just merged it. :wink:

Attached is a patch that fixes it.

Also, I have found that reading from the ADC kill the Touch screen, so there
is obviously a bug here. I'll try to
fix it in a jiffy, but I'm afraid I cannot reccomend the current merge..
Again super sorry.. : (

Regards,

Robert, here is a patch that fixes the bug with disabling the touch screen. However, I’m quite certain that the touch-screen is not working as expected right now. It does register “pen-up” events, so it is possible to press stuff, but not possible to drag stuff. Could be pressure or Z issue. I’ll look into it. Since this has been merged already I guess it’s better to try to fix it than to push back or what? In my opinion it would be really nice to have a working ADC on kernel 3.8…

0000-fix-reading-adc-disables-touch-screen.patch (895 Bytes)

Hi,

> * The history is I started with Gentoo, which I believe has the best
> cross-building infrastructure of the major desktop/server Linux
> distributions out there, but Koen was able to build and optimize
> packages using OpenEmbedded far faster than I could. No one else has
> even really stepped up to the plate. While Robert does an amazing
> job at supporting Ubuntu, Debian *and* Fedora using the upstream
> distro build tools and the kernel integration work where he
> collaborates with Koen, none of the upstream distro maintainers has
> taken it as an on-going effort to support Beagles out of the box in
> a clean fashion. Ubuntu had a start and I thought was going to get
> there, but I think the model is more one of commercial contributions
> to keep it going. Arch Linux is the closest I've seen so far
> outside of Angstrom.

It works both ways - Part of the reason why other distributions haven't
jumped to support beaglebone is the kernel situation, and naturally the
closed SGX/TI part.

Kernel stuff is improving, but slower than hoped.

With that said, we do E.G. have a beaglebone defconfig in Buildroot
(currently using the 3.2 vendor kernel).

Hi,

> * The history is I started with Gentoo, which I believe has the best
> cross-building infrastructure of the major desktop/server Linux
> distributions out there, but Koen was able to build and optimize
> packages using OpenEmbedded far faster than I could. No one else has
> even really stepped up to the plate. While Robert does an amazing
> job at supporting Ubuntu, Debian *and* Fedora using the upstream
> distro build tools and the kernel integration work where he
> collaborates with Koen, none of the upstream distro maintainers has
> taken it as an on-going effort to support Beagles out of the box in
> a clean fashion. Ubuntu had a start and I thought was going to get
> there, but I think the model is more one of commercial contributions
> to keep it going. Arch Linux is the closest I've seen so far
> outside of Angstrom.

It works both ways - Part of the reason why other distributions haven't
jumped to support beaglebone is the kernel situation, and naturally the
closed SGX/TI part.

Kernel stuff is improving, but slower than hoped.

With that said, we do E.G. have a beaglebone defconfig in Buildroot
(currently using the 3.2 vendor kernel).

I do hope the situation with the beagleboard.org (non-ti) vendor tree
makes for easy integration into buildroot for supporting the next-gen
bone as well as the existing bone on a newer kernel (initially 3.8).
Certainly our top goal is to get the support into mainline, but there
are enough major ARM architecture changes going on to get may more of
us engaged, especially for supporting things like devicetree, PWM and
IIO.

Jason, Robert. I have worked a lot on the touch screen controller without cracking it. The described way from the TRM of using the Pen down as an event has led me nowhere since it seems to fire on the start of conversion instead of at the end of conversion as it should.

I saw just now that there has been some activity on the Arago project in the last days where they have separated the FIFOs for ADC and TSC so I’m trying a port of that to 3.8. They are still using overflow events so I guess not even TI has figured out how to use the Pen down IRQs (chuckle).

Anyways I need this working for tomorrow morning for a demo, so even if it will not be excepted as a patch on the release, I still have to get it done. If anyone else is working on this, let me know and I would be very interested in hearing about it!

Jason, Robert. I have worked a lot on the touch screen controller without
cracking it. The described way from the TRM of using the Pen down as an
event has led me nowhere since it seems to fire on the start of conversion
instead of at the end of conversion as it should.

I saw just now that there has been some activity on the Arago project in the
last days where they have separated the FIFOs for ADC and TSC so I'm trying
a port of that to 3.8. They are still using overflow events so I guess not
even TI has figured out how to use the Pen down IRQs (chuckle).

Anyways I need this working for tomorrow morning for a demo, so even if it
will not be excepted as a patch on the release, I still have to get it done.
If anyone else is working on this, let me know and I would be very
interested in hearing about it!

Touchscreen on LCD3 Cape rev A2 works out-of-the-box on the 3.8-beagle kernel.

Jason, you are right, but it is not very responsive and also interferes with the other analog channels. Have you Tried reading from the analog input while using the LCD3? Individually they work pretty well, but they do not play well together…

I have a patch for it if you decide it’s worth the effort. Not a lot of people would come across this issue I guess, but for me it is critical.

0001-import-fifo-channel-separation-for-touch-screen-from-arago-linux-am33.patch (14.4 KB)