Welcome, Guest

Author Topic: going mainline  (Read 2231 times)

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
going mainline
« on: February 17, 2018, 09:32:56 PM »
Hi!

It seems that with kernel 4.16 simple framebuffer should work on A64. See: https://mail-archive.com/linux-kernel@vger.kernel.org/msg1574304.html

So I'm thinking now might be a good time to try the mainline kernel on the teres - at least we should see something even without serial console / debug connection. However first thing I noticed is: There isn't even a device tree file for the teres1 yet. (Actually quite surprising: I recall olimex sending a number of prototype laptops to developers before sales started. How did these people get anything done without even a device tree file to boot the thing?)

I just checked and compared the devicetree files from the official software image (seems to be some general hardware definition from allwinner, not actually describing the real HW - but maybe some things have been tweaked to get the laptop working) and sun50i-a64-olinuxino.dts from mainline kernel. There seem to be lots of differences in regulator definitions for example. I guess merging these will not be entirely trivial. Has somebody already started working in this?

I guess I will start with sun50i-a64-olinuxino.dts and see what's different in a64-teres. What bothers me a bit is, that I basically need to get it right on the first attempt: If the kernel doesn't boot, I will get little feedback to figure out what's wrong, because I can't attach a serial cable to the laptop.

OTOH it probably would make sense for olimex to take the lead in this - after all you guys should know the information in the device tree file already. Actually it would be very reasonable if an open hardware product came with a proper device tree file by default. After all the device tree is just a machine readable description of the product.

Harald

starkwether

  • Newbie
  • *
  • Posts: 18
  • Karma: +1/-0
Re: going mainline
« Reply #1 on: February 18, 2018, 04:54:27 AM »

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
Re: going mainline
« Reply #2 on: February 18, 2018, 11:36:30 AM »
This page is very helpful - it is actually how I found the patch I linked in the first post.

However it doesn't provide any information about people working on a64-teres board support.

khumarahn

  • Jr. Member
  • **
  • Posts: 68
  • Karma: +6/-0
Re: going mainline
« Reply #3 on: February 18, 2018, 03:30:56 PM »
Why can't you attach a serial cable?

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
Re: going mainline
« Reply #4 on: February 19, 2018, 02:07:09 AM »
Why can't you attach a serial cable?

How would you go about it?

AFAICS the debug connector is the headphone connector with some line (GPIO?) selecting the function. I don't know how setup debug output and even if I knew, I'd net to get the right connector somewhere and then I'm still not confident to do it right: I'd hate to fry my shiny new laptop because I got some wiring wrong.

But if you got a serial console/debug console working, maybe you can help me out with testing?

starkwether

  • Newbie
  • *
  • Posts: 18
  • Karma: +1/-0
Re: going mainline
« Reply #5 on: February 20, 2018, 07:59:04 PM »

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
Re: going mainline
« Reply #6 on: February 21, 2018, 11:51:33 AM »
The efforts around pine64 have provided lots of drivers that we need for the teres. We basically get a free ride here. However of course they wont write a device tree file for us: We need a proper device tree to tell the kernel to actually use these drivers ...

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
Re: going mainline
« Reply #7 on: February 28, 2018, 01:43:52 PM »
JFTR: User dddddd from the olimex irc channel (user deesix here on the forum) has figured out how to make a debug cable for the theres: (Log is here: https://www.olimex.com/irc?date=2018-01-20)

We are now working together to get mainline kernels booting.

Harald

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
Re: going mainline
« Reply #8 on: March 10, 2018, 05:55:18 PM »
Good news everybody: deesix and me got the debian kernel to boot (quite easy) and with a bit of tweaking things and enabling a few more drivers also got the display working on mainline kernel (a bit tedious) with simple framebuffer together with most of the hardware in the teres.

I will make a debian image available publicly after the weekend for everybody to test, develop on and use. Patches probably will be sent to linux (device tree file) and debian (enabling a few modules in the arm64 kernel package) soon, but early feedback might be helpful to find the less obvious issues.

khumarahn

  • Jr. Member
  • **
  • Posts: 68
  • Karma: +6/-0
Re: going mainline
« Reply #9 on: March 10, 2018, 06:00:14 PM »
great news! Can you share the kernel sources with compilation instructions?

What still does not work?

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
Re: going mainline
« Reply #10 on: March 10, 2018, 11:24:35 PM »
great news! Can you share the kernel sources with compilation instructions?

I think a vanilla 4.15.x kernel should work (though actually we used different 4.16 release candidates most of the time).

I'm still in the process of cleaning up what we did (removing all the dead ends, etc.) - after that, I will send patches upstream and can link the kernel .config here. I can also link all patches here.

Quote
What still does not work?

On the annoying side:
  • After the system goes into suspend (eg. the laptop lid is closed), the power button doesn't wake it up anymore, nor does plugging in power. (The power button is recognised as such by linux and to shut down the system works.) I have declared the AXP803 as wakeup-souce in DT, but either that doesn't work or suspend creates some broken state. (Probably the former, because I guess a broken suspend state would cause a reboot?). I didn't try other wakeup sources though.
  • Many other features of the AXP803 and in particular fuel gauge (quite important for a mobile device IMO) haven't been activated yet. Mostly because it is unclear if they are compatible with older AXP version or need changes to the driver. The documentation is somewhat sparse on which featurs of which AXP version are actually supported. Shouldn't be too difficult to work on this however, if somebody is inclined to do so.


Other things:
  • simple framebuffer on HDMI needs more work - especially on the bootloader side.
  • I didn't look into sound at all. Might be easy, might not be easy. It works on H3, so might be possible to use the same drivers on A64 or at least easy to port.

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
Re: going mainline
« Reply #11 on: March 12, 2018, 09:29:16 PM »
JFTR: Here is the link to all the patches sent to linux:
https://lkml.org/lkml/2018/3/12/653

(Don't let that discourage you to report any problems. Would be the first time that such a patch from me passes review on the first attempt.)

deesix

  • Newbie
  • *
  • Posts: 6
  • Karma: +1/-0
Re: going mainline
« Reply #12 on: March 12, 2018, 10:27:37 PM »
Great, lambda. Icenowy sent a PR with a simplified ATF patch to apritzel's repo.

Thanks! both!

lambda

  • Full Member
  • ***
  • Posts: 153
  • Karma: +12/-0
    • Support my work
Re: going mainline
« Reply #13 on: March 12, 2018, 11:55:54 PM »
Great, lambda. Icenowy sent a PR with a simplified ATF patch to apritzel's repo.

Nice, I wasn't aware of that. The calls to udelay() are missing though. I guess she knows what she is doing - she has worked on supporting this chip the most it seems.

deesix

  • Newbie
  • *
  • Posts: 6
  • Karma: +1/-0
Re: going mainline
« Reply #14 on: March 20, 2018, 09:02:14 PM »