• Content count

  • Joined

  • Last visited

About TonyMac32

  • Rank
    Embedded member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

2106 profile views
  1. First we need the output of armbianmonitor -u Then, we can have an idea what's going on. What is attached, what is powered by, etc.
  2. bug

    I put this on the bug, but did you try
  3. yeah. I'm sure, I can probably find some examples for that. The permissions are in the build system now, so item 0 should be unneeded.
  4. A major bonus with these new H6/RK3399 boards is that we shouldn't have to worry about micro-usb. if you want the "cool stuff" you need 12V.
  5. A20: @Igor - legacy kernels should go out due too overall bad kernel quality - reboot/poweroff problems on some boards H3: @chwe - CSI (camera) doesn't work on mainline, gc2035 needs an small script in legacy to start up properly - Armlogic: @TonyMac32 - Mainline support effort is still relatively new. Things like USB, audio, etc are WIP. - "Legacy" kernel that is stable is old and EOL (3.14) and I haven't fooled with it. In that world and all others Amlogic, @balbes150 is the master. - Newer legacy kernel is still a work in progress (4.9 w/bugs) - u-boot blobs are lame and make using mainline u-boot difficult (need both legacy 2015 and mainline u-boot to get a working image) - Lower quality of open source information, all more or less community driven by a very small group, unlike with say Rockchip with a large amount of published info from Rockchip themselves. Rumor/commits say this may change with newer IoT processors. Freescale: @Igor - the legacy kernel is getting obsolete. No point to have it. - possible to implement hw video acceleration on mainline kernel - Solidrun has new 4.9 kernel, but can be safely ditched for mainline Rockchip (I suggest only the one we support at the moment, not RK3399): @chwe - CSI (tinkerboard, rk3288) is supported (RK 4.4 bsp kernel) by kernel (OV6547 OV5640, imx219 - RPI-cam V1.3 resp. V2) but doesn't show up properly when booting) @TonyMac32 - Igor and tkaiser are already seeing this, but mkimage/uboot/trust can be finicky. luckily that's a "figure it out and move on" situation, but it is likely to cause headaches. - 4.4 kernel is an increasingly old kernel, now 2 LTS's in the past, however still much better than a lot of others (also has a lot of activity) - RKwifi is something I don't know the reason for. I don't know why it exists, I don't know what it does (other than cause problems). It is a wrapper for some wifi drivers/an rfkill system - Rockchip likes to use their own subsystems in many things, like the "MPP" system for media playing. This has different capabilities per SoC, so may not behave predictably to simply be able to say we know how to use it. Marvell ARMADA: @Igor - missing SFP support in mainline Armbian related scripts: @chwe - h3consumption is legacy only -
  6. I'll start over with a clean file and see. @JMCC that cleared it right up. Very nice. it gets quite upset about the touchscreen being attached though, I'll probably have to figure that out. Perhaps a script the user can run to enable this stuff would be best glmark2-es2 score was 54, it seemed to be locking fps to the screen refresh, webgl worked perfectly, youtube was smooth at 1080p even without hardware decode.
  7. I'm getting "Section" is not a valid keyword in this section"
  8. Le Potato GPIO pins on /sys

    I was going to do some more checking on this right away, but I forgot to take the highspeed out of the SD device tree and now it won't boot. I'll be back after dinner when I swap my old device tree back in. (I have a very old potato without the 1.8volt line. You would think after messing up so often I'd stop. Nope.)
  9. Le Potato GPIO pins on /sys

    @Neil Armstrong I get gpiochip0: GPIOs 0-9, parent: platform/c8100000.aobus:pinctrl@14, aobus-banks: gpio-2 ( |librecomputer:blue ) out lo gpio-3 ( |? ) out lo gpiochip1: GPIOs 10-110, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks: gpio-29 ( |HDMI_5V ) out lo gpio-45 ( |reset ) out lo gpio-58 ( |cd ) in lo gpio-83 ( |librecomputer:system) out hi from/sys/kernel/debug/gpio Thanks again, for the quick reply.
  10. Le Potato GPIO pins on /sys

    Right. I just couldn't find the entries, truthfully I wasn't certain where to look. Thanks Neil for giving direction so quickly. I'll take a look after bit, at the moment installing curtains for the wife... ;-) Sent from my Pixel using Tapatalk
  11. Le Potato GPIO pins on /sys

    Yes, the device tree has a comma delimited table in it with the names, but that means they should exist in the kernel somewhere, I haven't spent enough time trying to find them. Maybe I should just ask @Neil Armstrong to fill in for my lack of knowledge whenever he has a free moment. (Obviously he is quite busy doing the real work, so don't expect anything/anything soon)
  12. Good question, I have quite lost track of that work in the last few weeks. That is, of course for mainline, but will be relevant to this project.
  13. Tinkerboard video : very slow ?

    That is the goal. I have 2 things on my list of "has to work" and 1 on the "should work" before we roll out a new image: Audio is a must and the Mali permissions. The Bluetooth situation is complicated by the Rockchip rfkill stuff, for some reason the simple service that works on other boards with rtl8723bs does not work at all on this one. If it doesn't work properly with a few adjustments I will leave it as it is.
  14. Good, I haven't had time to try it yet, on the list for today. Then figuring out how far I can integrate it. I'm going over the documentation to see, I know there are extra packages installed for sun*i mali, I'd ideally want to do that. @zador.blood.stained and @Igor are the wizards that maintain the build system itself, I only work within it on board support, and haven't had much experience with the more advanced parts. I will at least get the permissions sorted today so the level 0 instruction is unnecessary.
  15. Le Potato GPIO pins on /sys

    This is something I haven't quite figured out either. The potato device tree assigned a user-friendly name to each pin, however for the life of me I can't find it in the device listing.