Option to choose framebuffer device
tux-linux opened this issue · comments
I realized I had a couple of old LeapPads lying around in my house and wondered if I could get a shell with a serial connection. Turns out that yes, it's possible and it even has built-in USBNet modules. Although having a crappy CPU and only 43 MiB of RAM, it runs Linux 2.6.31 and I managed to compile FBInk for it using one of the musl toolchains for armv5l.
For the record, here's what it looks like:
To use it, though, I had to change the framebuffer device to /dev/fb1 but FBInk always uses fb0. I did get around this by changing the file descriptor in fbink.c but it would be nice to have an option to change it at run-time (and default to fb0 when not specified).
Just a suggestion...
Could probably do that via an env var, yeah ;).
IIRC, there's even a semi-standard convention for it... somewhere :D.
Could probably do that via an env var, yeah ;).
IIRC, there's even a semi-standard convention for it... somewhere :D.
The LeapPad seems to have a multi-layer FB somehow...
~ # cat /proc/version
Linux version 2.6.31-leapfrog (fLPAD@lf2000-release) (gcc version 4.5.4 20110722 (prerelease) (GCC) ) #1 Mon Nov 25 17:26:03 PST 2013
~ # ls /dev/fb*
/dev/fb0 /dev/fb1 /dev/fb2
FWIW, if you want to see how it looks in a video: https://www.youtube.com/watch?v=6EfoECqD9Pk
From my side, I'll try looking at fbink.c and see if I could make some changes and make a pull request to offload you that work ;)
Stupid question: what's the cassette tape for? :D.
Stupid question: what's the cassette tape for? :D.
To help it stay put ;)
Handling serial connections with toothpicks isn't a very steady method :D
(Although, it works very well)