<wpwrak>
so it seems. an OAL (Ottawa Arduino Symposium) would probably drown in money from charitable helpers
<larsc>
or the Ottawa Potatosalad Symposium
<eintopf>
df shows:
<eintopf>
overflow 1024 1024 0 100% /tmp
<eintopf>
mhh
FDCX has joined #qi-hardware
<apelete>
larsc mth: I'm having the following issue while trying to build dma-jz4740.c as a module -> http://paste.debian.net/120085/
<apelete>
any idea why the dma driver is considered GPL-incompatible here ?
<larsc>
no MODULE_LICENSE("GPL")?
<apelete>
yes there is
<apelete>
MODULE_LICENSE("GPLv2");
<larsc>
try to cherry-pick commit e2f9922ad4526e747f9727a5481979727db56ec6
<apelete>
fixes it, thanks
wolfspraul has quit [Quit: leaving]
<apelete>
mth larsc: trouble again. loading the module with "insmod /media/system/virt-dma.ko && insmod /media/system/dma-jz4740.ko" reboots the kernel without kgdb kicking in
<apelete>
was expecting it to panic and let kgdb take over. any idea ?
<larsc>
really bad bug ;)
<larsc>
maybe you lockup some internal bus and the watchdog triggers the reboot
<apelete>
that's a nice way of saying I'm screwed :)
<apelete>
larsc: what is the virt-dma module used for anyway ?
<mth>
I have seen total system hangs when accessing the LCD controller too soon after its clock is started
<mth>
maybe more peripherals have problem when accessed when the clock is off or not running long enough
<mth>
"long enough" for the LCD controller was a very short wait, in fact the bug only occurred if the enable and the write were within the same cache line
DocScrutinizer05 has quit [Quit: Konversation terminated!]
DocScrutinizer05 has joined #qi-hardware
DocScrutinizer05 has quit [Changing host]
DocScrutinizer05 has joined #qi-hardware
arhuaco has joined #qi-hardware
FrankBlues has quit [Remote host closed the connection]