<jernej>
it seems that verbosity in platform.c was increased recently to explicitly warn this
<jernej>
so I guess that sun4i_gpadc driver needs to be fixed?
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Aria 5.0.1, revision: 5.0.1+git-7433-0df9f22f2, build type: debug, sources date: 20160102, built on: 2019-12-08 19:19:20 UTC 5.0.1+git-7433-0df9f22f2 http://www.kvirc.net/]
Mangy_Dog has joined #linux-sunxi
gnarface__ has joined #linux-sunxi
gnarface__ has left #linux-sunxi [#linux-sunxi]
gnarface is now known as Guest92123
Guest92123 has quit [Killed (weber.freenode.net (Nickname regained by services))]
gnarface has joined #linux-sunxi
<Ashleee>
you know you have quite a few devices when two 8port switches are all occupied all by Allwinner -based SoC boards...
<[TheBug]>
yeah... I have at least one.. how about EBins, do they count? if so I guess I am one my second..
<[TheBug]>
there are three in this room alone
<[TheBug]>
:Z
<[TheBug]>
(8 port switches)
<Ashleee>
I'll be switching (heh) out one 8port dumb switch for another 16port dumb switch, found on aliexpress one that's without its shell ... thought it was gonna be smaller but nope, it is about 17cm wide so can just about fit OrangePi Zero next to it and port LEDs will go ... no idea where
<Ashleee>
(I have 10" rack so about 24cm usable space between edges)
<jernej>
any idea why I don't get ethernet working on 5.8 with A20 olinuxino micro?
<jernej>
ethernet driver and phy driver probe fine, I see interface, just no communication
<Ashleee>
jernej, I've had similar issues on *some* H6 on debian setup initrd, where it would unload and then reload the driver, but it may just be a different issue
alexxy has quit [Quit: No Ping reply in 180 seconds.]
alexxy has joined #linux-sunxi
jstein has joined #linux-sunxi
jstein has quit [Quit: quit]
cmeerw has quit [Ping timeout: 272 seconds]
jbrown has quit [Ping timeout: 246 seconds]
DigitalMan1983_ has joined #linux-sunxi
<DigitalMan1983_>
hi folks, was wondering if anyone has any experience building U-boot for the A64?
<gnarface>
i built it for pinebook once or twice
<gnarface>
pretty sure that's A64 but maybe not the same thing as what you're using
<gnarface>
did you have a question about it?
<DigitalMan1983_>
yes pinebook is the same processor
<DigitalMan1983_>
I'm working with an Armbian build script that automatically generates a boot image (u-boot, kernel, root filesystem) based on a board selection
<DigitalMan1983_>
unfortunately, my board is not on the list, but the Teres is
<DigitalMan1983_>
very close with a few differences
<DigitalMan1983_>
so I used that and long story short, U-boot is not seeing my MMC and eMMC as it should
<DigitalMan1983_>
u-boot actually has the device tree for my specific board (Olinuxino)
<DigitalMan1983_>
my question is, would I be better off building my own u-boot, or if it would be possible to use the original configuration and scripts and somehow specify that device tree
<DigitalMan1983_>
apparently my make does not like CROSS_COMPILE=aarch64-linux-gnu- so it looks like i may need to install a toolchain
<gnarface>
DigitalMan1983_: did you use a defconfig? which defconfig? is there one for the Olinuxino?
<DigitalMan1983_>
there is not
<DigitalMan1983_>
only a DTS for u-boot
<DigitalMan1983_>
I'm using the Teres board configuration
<gnarface>
hmmm
<gnarface>
in my notes i'm also setting ARCH="arm64" but i don't know if that matters
<DigitalMan1983_>
I noticed that was missing...let me try that
<DigitalMan1983_>
same result - /bin/sh: 1: aarch64-linux-gnu-gcc: not found
<gnarface>
i had a problem with my pinebook emmc and microsd slots being in a different order than i expected
<gnarface>
could you be missing a package from your distro? something important from the toolchain?
<DigitalMan1983_>
yes, that seems to be the issue, I compared the console from a good boot on a working image to the one I built and it's evident that it's assigning different values to MMC and emmc
<DigitalMan1983_>
I know from the past typically I have to install a toolchain
<gnarface>
well i also built it in a chroot
<gnarface>
so the toolchain was installed in the chroot
<gnarface>
an i manually copied a qemu binary into there
<DigitalMan1983_>
everything is so streamlined with armbian that it's hard to know where to pry your way in and change things
<DigitalMan1983_>
I came from a Rockchip 3188 with kernel 3.0 so everything was done manually
<gnarface>
i needed /usr/bin/qemu-aarch64-static in the chroot, and binfmt-support running
<gnarface>
oh, and it didn't work before gcc version 7 something