<LordKalma>
we're going to give up the boot logo at u-boot time
<LordKalma>
because we have better things to do
<LordKalma>
and we'd also rather have a driver that works by itself
<LordKalma>
and doesn't need it's u-boot counterpart to work
<jernej>
if you want to submit driver to mainline linux (which you should), driver has to be standalone, e.g. not dependent on some bootloader magic
<jernej>
so that's the right approach
<cheetahpixie>
apritzel LordKalma alright. I have tackled, in shell too, harvesting partitions from devices with unstable connections and fragile buffers.
apritzel has quit [Ping timeout: 480 seconds]
<cheetahpixie>
it's a hacky concert of lots of busybox commands on the target side and xxd on the host side. sure, data transfer is doubled, but you won't crash adb through it since you set buffer sizes.
<cheetahpixie>
and in order to dodge possible bash/shell weirds (such as null characters), I convert to hex and back to make sure the binary data arrives intact.
<LordKalma>
jernej, what's the politis of upstreaming drivers that technically were reverse engineered?
apritzel has joined #linux-sunxi
<LordKalma>
and not with the double-blind loophole
<LordKalma>
jernej, the driver was stamped with the GPL2 macro, the U-Boot is technically GPL2, and atm the driver is significantly different since we're putting everythign together, and even doing some stuff directly from the datasheet
<LordKalma>
and also, we're not using even using the same name
<LordKalma>
but still...
<LordKalma>
that concerns be a bit about the upstream
kilobyte_ has joined #linux-sunxi
<LordKalma>
other than that, I'm more than happy to
<cheetahpixie>
what I was hoping to do was to take this a33 trash find no name tablet and install postmarketos.
<cheetahpixie>
and then to have an actual bleuprint for how to then do this with other devices (zero to linux"
<cheetahpixie>
I also have an a20 that doesn't have working serial rx for some reason.
<cheetahpixie>
so I can't type commands
<LordKalma>
I would definitely turn my cheap tablet into a linux machine if it worked okay haha
<cheetahpixie>
suspect a trace got cut or something somewhere
<cheetahpixie>
wing_inet it was. it's probably in old freenode logs.
<cheetahpixie>
tldr: the drivers exist. what doesn't is all the device tree stuff.
<cheetahpixie>
so if the extracted ones can be dependably converted to linux dts/dtb, we should be good to gentoo up a kernel or something and let the rest of postmarketos do what remains.
evgeny_boger has joined #linux-sunxi
<LordKalma>
cheetahpixie, you can decompile a DTB trivially
<LordKalma>
it's making it pretty that takes a while after that
<cheetahpixie>
I'm also looking at possibly breaking open a fex and converting that.
<cheetahpixie>
and this tablet has kitkat stock.
evgeny_boger has quit [Ping timeout: 480 seconds]
warpme____ has quit []
grming has joined #linux-sunxi
<jernej>
LordKalma: Many drivers were reverse engineered. If you only reuse register numbers and there values, that's fine.
<jernej>
*their
<jernej>
you obviously won't use same functions
sunshavi_ has joined #linux-sunxi
grming has quit [Quit: Konversation terminated!]
<cheetahpixie>
isn't uboot in nanda?
<cheetahpixie>
binwalk isn't finding the device tree
warpme____ has joined #linux-sunxi
vagrantc has joined #linux-sunxi
<apritzel>
cheetahpixie: I think those old devices don't use devicetree, but FEX files
<apritzel>
cheetahpixie: have you tried one of the existing A33 devicetrees? IIUC, many of them were based on common reference designs
<apritzel>
cheetahpixie: there is sun8i-reference-design-tablet.dtsi in the kernel tree, also check what includes that
<cheetahpixie>
I wanted to rip this device's fex to make sure there won't be conflict
<cheetahpixie>
hence me quizzing.
<cheetahpixie>
where on nand is that fex/bin file?
<apritzel>
cheetahpixie: I don't know, but you scan the hexdump for a bunch of strings like "product", "card_boot0_para", "twi_para", each 40 bytes aparts, the gaps filled mostly with 0 bytes
<apritzel>
chj
<apritzel>
cheetahpixie: check script_bin.h in sunxi-tools.git (which provides a FEX compiler/decompiler)
<apritzel>
also there are .fex examples in the sources tree (under tests/sunxi-boards-fixed/sys_config)
apritzel has quit [Ping timeout: 480 seconds]
<cheetahpixie>
does the binary have those strings?
<cheetahpixie>
actually. okay
<cheetahpixie>
lemme strings some stuff
<cheetahpixie>
oop, nanda == instant results
<cheetahpixie>
is there no header to fex files?
JohnDoe_71Rus has quit []
<cheetahpixie>
wait.
<cheetahpixie>
yeah. momentary bout of stupid. nanda is a filesystem
<cheetahpixie>
yeah. script0.bin is here.
<cheetahpixie>
what is the magic.bin anyway?
gnarface has quit [Quit: Leaving]
gnarface has joined #linux-sunxi
<cheetahpixie>
oh yeah, why is the wiki down?
<libv>
cheetahpixie: flaky machine that we are about to replace
<apritzel>
(which is going to become the main site in a few days, if I understand libv's and mnemoc's plans correctly)
<fisiek>
ok thanks, I just started to make schematic of a64 board and wanted to download datasheets
<fisiek>
btw is there any other open source project of a64 sbc than olimex or something from pine64?
rajkosto has joined #linux-sunxi
<apritzel>
fisiek: open source hardware, you mean? And why do you want to know? Many board vendors publish at least schematics, maybe that already helps you?
<apritzel>
Also: why A64?
<fisiek>
a64 from what i've read has most mainline linux support besides a20
<fisiek>
also I know most vendors publish schematics but just wanted to know if there's any other open source sbc than that from olimex
<buZz>
the question was why , to prevent XY problem questions ;)
<buZz>
oh you want to -make- a a64 sbc, nice
<buZz>
wasnt cubieboard open gerbers aswell?
rajkosto has quit [Quit: Leaving]
rajkosto has joined #linux-sunxi
<fisiek>
idk but cubieboard 1-3 has a20 and cubieboard 4 has a80
rajkosto has quit [Quit: Leaving]
<fisiek>
and about why i want to use a64, so i need soc that can run linux, has camera support and can do image processing fast enough to send live encoded image via radio
rajkosto has joined #linux-sunxi
<fisiek>
its for my mobile platform/rover/robot project
<buZz>
so you need a esp32
<buZz>
esp32-cam board is ~10 usd, can process image, even run some AI-like stuff, and send live video over wifi
<buZz>
plus you have BT , a whole second core available, and loads of gpio
<buZz>
and supereasy to make a board for ;)
<fisiek>
esp32 is really bad at image processing, and i want to send it over uhf its just not going to work
<buZz>
oh, retro :D
<buZz>
well esp32 can bitbang composite video out a pin :P
<buZz>
just plonk a VHS modulator on it, let it make uhf signal
<buZz>
but yeah, a10/20/64 have composite video on a pin too
<fisiek>
composite is analog and i want to use digital modulation so esp is not going to cut it
<fisiek>
I need to ask a friend for a tool/project for live video encoding and modulation because I forgot its name xD
<fisiek>
it only works on linux and needs a "little more" processing power than esp32
Arthur[m]12 has quit [Server closed connection]
Arthur[m]12 has joined #linux-sunxi
pgwipeout[m] has quit [Server closed connection]
pgwipeout[m] has joined #linux-sunxi
<fisiek>
and i've either miss read something or forgot something but OpenHD is fpv via wifi xD
<fisiek>
my bad
rajkosto has quit [Quit: Leaving]
rajkosto has joined #linux-sunxi
<fisiek>
but still esp isn't going to work because i can write some bad code for encoding image and send it via APRS
<buZz>
so you're planning on using ROS.org on it?
<fisiek>
no, why?
rajkosto has quit [Quit: Leaving]
<buZz>
oh i thought you wanted to make a rover/robot
<fisiek>
right, but for my application I don't really need it
<fisiek>
i'm probably going to use mcus for something like controlling motors or idk power system
<fisiek>
a64 is for handling video and controlling manipulator
<fisiek>
also its going to talk with mcus etc
<fisiek>
it's just going to be central processing unit :P
<apritzel>
fisiek: maybe you can use some of the SoCs that come with on-package DRAM? Like V3s or T113s? That saves you a lot of hassle with the board design.
<fisiek>
apritzel: I really want to try routing and testing board with external DRAM also 64MB as in V3s is pretty small
<fisiek>
I might try making V3s board just to get feel of it
<apritzel>
fisiek: T113s has 128MB, and two A7 cores
<apritzel>
fisiek: I still don't get why you were asking for *more* examples? Doesn't Olimex for instance provide enough, to guide you in the PCB design?
bauen1 has quit [Ping timeout: 480 seconds]
<apritzel>
From what I hear they are one of the better board designers
<fisiek>
no i'm not asking for more examples, I can make what i need based on their design
<fisiek>
but just wanted to know if there are more projects like this
<fisiek>
i don't need it, just wanted to know
bauen1 has joined #linux-sunxi
<smaeul>
I think most hobbyist projects are focused on F1C100s/V3s/D1s because of the built-in DRAM
<smaeul>
there are a bunch of commercial robot vacuums based on Allwinner R-series chips
<fisiek>
smaeul: oh ok, that makes sense
<buZz>
fisiek: ROS is mostly motion planning etc, not motion -control- ;)
<buZz>
and stuff for making maps from sensordata etc
<buZz>
object avoidance
<fisiek>
buZz: oh ok i didn't knew that i thought it's about motion control