<uis>
AFAIK no. Ffmpeg already can use v4l2 decoding.
<macc24>
oh
repk has joined #linux-rockchip
<macc24>
i'll play around it Soon™
macc24 has quit [Ping timeout: 272 seconds]
macc24 has joined #linux-rockchip
repk has quit [Read error: Connection reset by peer]
repk has joined #linux-rockchip
WoC has quit [Remote host closed the connection]
field^Mop has joined #linux-rockchip
<macc24>
could anyone dualboot chromeos and linux on arm chromebook?
<mps>
macc24: iirc I did this few years ago. using one of kernel partitons for linux and one of root fs
<mps>
but had to 'switch' them by cgpt and changing priotity for kernels
<mps>
ofc, better option is to keep chromeos on internal 'disk' and using external 'disk' for linux, but I think you know this
<macc24>
mps: how dod you do this?
<macc24>
did*
<mps>
macc24: as I wrote I forgot details but chromeos have two partitions for two kernels and two partitions for two root FSs
<mps>
they are for rescue in case upgrade of OS doesn't work
<mps>
these two kernel partitions have some flags/attrs for example, 'Attr: priority=10 tries=5 successful=1'
<mps>
iirc priority is what defines which one will be used to be booted
<macc24>
mps: were there issues with updating?
<macc24>
did chromeos attempt to nuke the other partition?
<mps>
probably will nuke it, but I didn't tried this
<macc24>
yeah i'll try out this setup
<mps>
I only played with this on samsung peach pi (exynos5800) arm32 chromebook, not on gru-kevin or elm-oak
chewitt_ is now known as chewitt
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 245 seconds]
kevery1 is now known as kevery
alpernebbi has joined #linux-rockchip
vstehle has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 276 seconds]
kevery1 is now known as kevery
WoC has joined #linux-rockchip
swiftgeek has quit [Ping timeout: 246 seconds]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 245 seconds]
kevery1 is now known as kevery
swiftgeek has joined #linux-rockchip
WoC has quit [Ping timeout: 240 seconds]
damex has quit [Quit: damex]
damex has joined #linux-rockchip
WoC has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 256 seconds]
alpernebbi has quit [Ping timeout: 245 seconds]
vagrantc has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
mrueg has quit [Remote host closed the connection]
mrueg has joined #linux-rockchip
swiftgeek has quit [*.net *.split]
ldevulder has quit [*.net *.split]
lkcl has quit [*.net *.split]
hipboi has quit [*.net *.split]
mraynal has quit [*.net *.split]
ldevulder has joined #linux-rockchip
swiftgeek has joined #linux-rockchip
mraynal has joined #linux-rockchip
lkcl has joined #linux-rockchip
hipboi has joined #linux-rockchip
ldevulder has quit [Quit: Leaving]
MachX has joined #linux-rockchip
<macc24>
mps: can i ask you to test one thing on kevin?
<macc24>
it involves mkfs.f2fs /dev/mmcblk2p3
<mps>
macc24: if I can, sure
<macc24>
yeah can you do this?
<macc24>
it seems to hang on my machine
<macc24>
or like any other big partition on internal emmc
<mps>
I use f2fs on both partitions, root and home
<macc24>
mkfs.f2fs seems to hang on 'Discarding device'
<mps>
yes, I had this on some old kernels
<mps>
you have to give switch to not discard
<macc24>
on 5.12-rc1 it hangs too
<macc24>
mkfs.ext4 completes fine with discard
<mps>
ahm, then '-t 0'
kevery has quit [Ping timeout: 245 seconds]
kevery has joined #linux-rockchip
<mps>
didn't had to reinstall for long time so forgot about this, but last time I had to use '-t 0'
<macc24>
:/
<mps>
with chromeos kernels this is not needed, iirc
FaN has quit [Quit: Connection closed]
matthias_bgg has joined #linux-rockchip
alpernebbi has quit [Remote host closed the connection]
hexdump0815 has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 264 seconds]
<macromorgan>
any reason why readl in a driver works then all of a sudden oopses? Trying to use a rockchip_sfc.c driver and while it probes and reads the chip successfully it fails when I actually try to read the chip.
<macromorgan>
it checks a register at offset 0x24 successfully several times during the driver probe and chip probe, but the instant I try to transfer data off the chip reading that register causes an oops
<macromorgan>
(I'm 100% lost on what I'm doing if that's not clear)
<macc24>
hi macromorgan
<macromorgan>
howdy
<macromorgan>
still banging my head against this sfc crap
<macromorgan>
calling readl or readl_poll_timeout on a specific register seems to succeed then fail, and I'm not smart enough to figure out why
* macc24
wubbles mmind00
* mmind00
doesn't know what a wubble is ;-)
<macc24>
mmind00: essentially a poke
<mmind00>
macromorgan: best guess some the clock may be off?
<mmind00>
macromorgan: in the function doing the reading just insert a readl for that 0x24 register and look if that works or already oopses (just add some printk around it)
<macromorgan>
I did that, it triggers the oops
<macromorgan>
basically I have a readl_poll_timeout which was triggering an asynchronous external abort
<macromorgan>
I wanted to see what the register itself said though, so I put a pr_info function in to print just the readl value of that register
<macromorgan>
now the readl_poll_timeout doesn't cause the issue, because the readl does
<macromorgan>
(the readl being prior to the readl_poll_timeout)
<macromorgan>
the "kernel-panic-no-dma" is what I'm getting, and the code is what I'm trying. It runs well enough to actually detect the spi flash chip, but fails at the readl_poll_timeout part of the rockchip_sfc_wait_idle section