ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
apritzel_ has quit [Ping timeout: 260 seconds]
vireshk has quit [Ping timeout: 260 seconds]
vireshk has joined #armlinux
tchebb_ has joined #armlinux
tchebb has quit [Ping timeout: 248 seconds]
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
gclement has joined #armlinux
gclement has quit [Client Quit]
gclement has joined #armlinux
cbeznea has joined #armlinux
geertu has joined #armlinux
monstr has joined #armlinux
monstr has quit [Ping timeout: 252 seconds]
apritzel_ has joined #armlinux
frieder has joined #armlinux
gclement has quit [Ping timeout: 268 seconds]
mvaittin has quit [Ping timeout: 248 seconds]
luispm has joined #armlinux
monstr has joined #armlinux
jclsn has joined #armlinux
mvaittin has joined #armlinux
mvaittin has quit [Remote host closed the connection]
headless has joined #armlinux
mvaittin has joined #armlinux
gclement has joined #armlinux
sszy has joined #armlinux
apritzel_ has quit [Ping timeout: 244 seconds]
headless has quit [Quit: Konversation terminated!]
<javierm>
geertu: hi, could you please remind me if for 4-grayscale displays the fourcc used should be DRM_FORMAT_C2 or DRM_FORMAT_R2 ?
<javierm>
I believe is the latter but wanted to confirm with you
<geertu>
javierm: R4
<geertu>
C4 is for 16-color CLUT
<geertu>
Sorry, R2
<javierm>
geertu: that's what I thought, thanks! Because noticed a driver using C2 for a greyscale and wanted to point out the wrong fourcc
<javierm>
if is about intensities of the single color (i.e: grey) then is a LUT and so R*, the C* are for CLUT as you said
<geertu>
With R*, there is no LUT
<javierm>
geertu: ah, I thought that you could still have a table that defined your grayscale levels
<javierm>
but maybe that's not called a LUT then
<geertu>
Gamma table?
<javierm>
right
<javierm>
that's the correct name indeed :)
Amit_T has joined #armlinux
markussp has quit [Ping timeout: 260 seconds]
markussp has joined #armlinux
monstr has quit [Ping timeout: 252 seconds]
luispm has quit [Ping timeout: 252 seconds]
TheCoffeMaker_ has quit [Ping timeout: 268 seconds]
jbowen has quit [Ping timeout: 265 seconds]
sjg1 has quit [Ping timeout: 265 seconds]
sjg1 has joined #armlinux
jbowen has joined #armlinux
monstr has joined #armlinux
monstr has quit [Ping timeout: 252 seconds]
mvaittin has quit [Ping timeout: 244 seconds]
TheCoffeMaker has joined #armlinux
luispm has joined #armlinux
TheCoffeMaker has quit [Ping timeout: 252 seconds]
TheCoffeMaker has joined #armlinux
monstr has joined #armlinux
TheCoffeMaker has quit [Ping timeout: 252 seconds]
TheCoffeMaker has joined #armlinux
<lag>
QQ: Is there a good way to print without an enforced new line? printk() and pr_err() both insist on a '\n' even with PRINTK_TIME and PRINTK_CALLER disabled.
monstr has quit [Ping timeout: 252 seconds]
TheCoffeMaker has quit [Ping timeout: 244 seconds]
headless has joined #armlinux
<ukleinek>
lag: there is pr_cont()
<ukleinek>
(But no first hand experience here)
<ukleinek>
I think the enforced \n only happens if you emit the next pr_$level without KERN_CONT
<lag>
That's just crazy enough to work - bear with
zx2c4 has quit [Ping timeout: 276 seconds]
nohit has quit [Ping timeout: 252 seconds]
zx2c4 has joined #armlinux
NishanthMenon has quit [Read error: Connection reset by peer]
steev has quit [Read error: Connection reset by peer]
jbowen has quit [Ping timeout: 260 seconds]
NishanthMenon has joined #armlinux
steev has joined #armlinux
ardb has quit [Read error: Connection reset by peer]
lpieralisi has quit [Read error: Connection reset by peer]
lpieralisi has joined #armlinux
ardb has joined #armlinux
lvrp16 has quit [Ping timeout: 252 seconds]
manchaw has quit [Ping timeout: 248 seconds]
robher has quit [Ping timeout: 265 seconds]
nohit has joined #armlinux
lvrp16 has joined #armlinux
manchaw has joined #armlinux
jbowen has joined #armlinux
robher has joined #armlinux
TuningYourCode has joined #armlinux
frieder has quit [Remote host closed the connection]
vingu has quit [Remote host closed the connection]
vingu has joined #armlinux
gclement has quit [Ping timeout: 260 seconds]
psydroid2 has joined #armlinux
TuningYourCode has quit [Quit: Konversation terminated!]
Peng_Fan has quit [Read error: Connection reset by peer]
dianders has quit [Read error: Connection reset by peer]
Tartarus has quit [Read error: Connection reset by peer]
puranjaymohan has quit [Read error: Connection reset by peer]
puranjaymohan has joined #armlinux
Peng_Fan has joined #armlinux
Tartarus has joined #armlinux
dianders has joined #armlinux
luispm has quit [Quit: Leaving]
TheCoffeMaker has joined #armlinux
TuningYourCode has joined #armlinux
TheCoffeMaker has quit [Ping timeout: 252 seconds]
TheCoffeMaker_ has joined #armlinux
apritzel has quit [Ping timeout: 245 seconds]
luispm has joined #armlinux
luispm has quit [Ping timeout: 246 seconds]
luispm has joined #armlinux
fvincenzo has quit [Quit: Lost terminal]
Amit_T has quit [Quit: Leaving]
<Stalevar>
Hi! I have /dev/mtd*, /dev/ubi0 and /dev/ubi0_0 and want to back up the system. Which method is better, tar, dd from ubi0_0, ubi0, mtdX, mtdXro or mtdblockX ?
<Stalevar>
I know about nand bad blocks so I guess it is going to work better with ddrescue instead of dd, if I am to back up raw device
<Stalevar>
However restoration is going to be difficult, as far as I remember one needs to create mtdram or nandsim or something device on PC
<Stalevar>
I would like to preserve all access rights, times and other metadata, not sure if busybox tar captures it all
TuningYourCode has quit [Quit: Konversation terminated!]
<Stalevar>
Also I guess mtd0 and mtd0ro things are character devices, so ddrescue method requires mtdblock0 device to be able to skip bad blocks
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
<Xogium>
Stalevar: mtdblock is *not* bad block aware
<Xogium>
I would try to copy the content of the ubi volumes/ubifs filesystem
<Stalevar>
Xogium, the important part is mtdblock has block read function, so ddrescue can skip bad blocks and start reading next good blocks
headless_ has joined #armlinux
headless has quit [Ping timeout: 272 seconds]
headless_ has quit [Quit: Konversation terminated!]
headless has joined #armlinux
<cambrian_invader>
Stalevar: if you want to back up, you should copy the filesystem
<cambrian_invader>
Stalevar: but if you don't trust that, then copy ubi0_0
<cambrian_invader>
if you want to do forensic analysis, then use nanddump
apritzel_ has joined #armlinux
<Stalevar>
cambrian_invader, doesn't ddrescue work? Or whatever tool which can read a block device skipping bad blocks?
<Stalevar>
I guess specific nanddump is better, just wonder if it's mandatory
<cambrian_invader>
if you are just doing a backup to restore later, then you should work with ubi
<cambrian_invader>
ddrescue will not handle bad blocks
<cambrian_invader>
but ubi abstracts that away
<Stalevar>
# mount -t ubifs -r /tmp/ubi0_0.img /flash/
<Stalevar>
mount: /flash: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.
<Stalevar>
I guess it needs nandsim
<cambrian_invader>
which is why it is easier to back up the filesystem
<Stalevar>
as in via tar?
<cambrian_invader>
or rsync or whatever
prabhakalad has quit [Ping timeout: 244 seconds]
cbeznea has quit [Ping timeout: 268 seconds]
headless has quit [Quit: Konversation terminated!]
System_Error has quit [Remote host closed the connection]