<hanetzer>
don't suppose anyone knows the max spi flash size for rk3399's? considering upgrading my gru-kevin's flash
vagrantc has quit [Quit: leaving]
kevery has joined #linux-rockchip
vagrantc has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
vagrantc has quit [Quit: leaving]
ganbold has quit [Ping timeout: 252 seconds]
ganbold has joined #linux-rockchip
lopsided98 has quit [Remote host closed the connection]
lopsided98 has joined #linux-rockchip
elektrinis has joined #linux-rockchip
niceplaces has quit [Ping timeout: 260 seconds]
niceplace has joined #linux-rockchip
dhivael has quit [Ping timeout: 260 seconds]
wens has quit [Ping timeout: 260 seconds]
elektirnis has quit [Ping timeout: 260 seconds]
samueldr has quit [Ping timeout: 260 seconds]
wens has joined #linux-rockchip
bshah has quit [Ping timeout: 260 seconds]
bshah has joined #linux-rockchip
sigmaris has quit [Ping timeout: 246 seconds]
samueldr has joined #linux-rockchip
sigmaris has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-rockchip
chewitt has quit [Client Quit]
chewitt has joined #linux-rockchip
chewitt has quit [Client Quit]
ganbold has quit [Remote host closed the connection]
ganbold has joined #linux-rockchip
levd_ has quit [Ping timeout: 240 seconds]
vicencb has joined #linux-rockchip
levd_ has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
aalm has quit [Quit: xyz 2.7]
field^Mop has joined #linux-rockchip
leah2 has quit [Ping timeout: 240 seconds]
leah2 has joined #linux-rockchip
kevery has quit [Ping timeout: 265 seconds]
<mmind00>
robmur01: out of curiosity, did you already get a Go-Advance or is it just on your wishlist? ;-)
<robmur01>
mmind00: I dithered in the "want one but I have too many toys already" stage until the first batch conveniently sold out
<robmur01>
so now I have 3 months to get some more current projects wrapped up :)
<robmur01>
place your bets on whether the second run still uses the same panel...
<mmind00>
robmur01: :-D ... mainline was soooo easy ... uboot + atf + kernel 5.6-rc was pretty straight forward (except spending too much time on the dsi-panel-driver)
<mmind00>
robmur01: :-P ... don't make me worry
<mmind00>
but then again, looking at recent history, I already got a lot of excercise doing panel drivers
* robmur01
is also eagerly holding out in case Rk35xx TV boxes start appearing
* mmind00
is hoping for rk3588 chromebooks ;-)
<mmind00>
not the least because that would mean a lot more Rk upstream involvement again
nashpa has quit [Ping timeout: 265 seconds]
<phh>
mmind00: you got mainline buttons/joystick yet?
<mmind00>
phh: buttons yes ... just gpio-keys
<phh>
mmind00: i've been wondering how to represent such things in dts, since you want only one /dev/input/ for two drivers
<mmind00>
phh: someone just need to give the saradc driver some love to handle iio-buffers
<phh>
uh fun, I thought adc joystick was in mainline since a long time ago
<phh>
but great
<phh>
mmind00: how does userspace know which devices to merge into individual gamepads?
nsaenz has quit [Remote host closed the connection]
<mmind00>
phh: I guess udev ... just open all event devices, get the codes (buttons are clearly exporting its value ... aka BTN_DPAD_LEFT, AXIS_X, etc) and map them accordingly
nashpa has joined #linux-rockchip
<mmind00>
and I would guess there should already be abstraction for that, as they is probably not a new problem ;-)
<mmind00>
like embedded devices already have multiple "keyboard"-sources for example ... (gpio-keys, keys exported from the rk817 pmic, or so)
<phh>
Usually it's easy because events are just broadcasted. You don't care where power button event is going to. However knowing if events are going to player 1 or player 2, not so much
lkcl__ has quit [Ping timeout: 255 seconds]
<robmur01>
I had the impression that it wasn't unusual for 'regular' gamepads to show up as multiple input events anyway
<robmur01>
but I have no idea where I got that from...
nsaenz has joined #linux-rockchip
lkcl__ has joined #linux-rockchip
<urjaman>
i remember mentions it being weird/a problem way back in like 2010ish with the pandora handheld (that has one driver for the gpio-based gamepad buttons, another for the analog "nubs" and a third for the keyboard...)
<urjaman>
but i dunno if things have changed since
<urjaman>
and now that i think of it the current idea for solving this with the "pandora successor" (maybe it'll happen soon(TM) :P) is to have an userspace input daemon to wrangle the multiple devices into one
<urjaman>
(and uinput or something to feed the kernel from the daemon...)
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-rockchip
lkcl__ has quit [Read error: Connection reset by peer]
<phh>
urjaman: well, I wanted to do that as well, but then I can't see how not to make this device-specific, since there isn't much way to know what should be gamepad 1, and what should be gamepad 2, except by actually knowing the hardware
kevery has quit [Ping timeout: 260 seconds]
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-rockchip
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-rockchip
lkcl__ has quit [Read error: Connection reset by peer]
ganbold has quit [Ping timeout: 260 seconds]
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-rockchip
lkcl has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 265 seconds]
nashpa has quit [Ping timeout: 272 seconds]
nashpa has joined #linux-rockchip
ldevulder_ has quit [Remote host closed the connection]
ldevulder_ has joined #linux-rockchip
vicencb has joined #linux-rockchip
ldevulder_ has quit [Remote host closed the connection]