<rjeffries>
GNUtoo|bug20 what is the connectivity between BugBase and the add-on modules?
<whitequark>
hm.
<kyak>
wow
<kyak>
it only took three days to deliver a parcel via Fedex
<kyak>
can't believe it
<kyak>
i guess this is why delivery cost is bigger (50.98 EUR) than the parcel cost (50 EUR, atben+atusb)
<kyak>
unfortunately, they didn't catch me at home
<kyak>
so i'll get it on monday
<GNUtoo>
valhalla, hi
<valhalla>
hi GNUtoo
<GNUtoo>
I'll PM you
<[g2]>
rjeffries ping.
<whitequark>
just wondering
<whitequark>
!ping
<[g2]>
hey whitequark
<whitequark>
[g2]: hi
<[g2]>
whitequark, you were picking on me for "pinging" :)
<whitequark>
[g2]: nope, i was wondering if qi-bot will reply the command
<[g2]>
whitequark, Ah... didn't know a bot was running :)
<whitequark>
doesn't actually know what "hey" can mean, depending on the context
<[g2]>
whitequark, It's like "hi"
<wpwrak>
GRRR. Maximum number of clients reachedError: Can't open display: :0.1
<wpwrak>
traitor !!
<stefan_schmidt>
muhahah
<stefan_schmidt>
RichardSharpe: hi
<stefan_schmidt>
wpwrak: hi
<stefan_schmidt>
wpwrak: lokking through your spi master driver now
<stefan_schmidt>
wpwrak: does it contain the irq handling we talked about that could also be used for atusb?
<wpwrak>
yes :)
<wpwrak>
and behold its beauty - it even allocates irq 0 on the ben :)
<wpwrak>
no idea how portable this is, though. maybe i was just incredibly lucky
<stefan_schmidt>
0 is always fun
<stefan_schmidt>
on cc2420 one irq is also on 0
<stefan_schmidt>
and trying to allocate the gpio freaks the gpio framework out
<stefan_schmidt>
not sure if this is fixed by now
<stefan_schmidt>
As the "alloc" is only for internal reference but not function I never came around to fix it :)
<wpwrak>
ah ? didn't have any trouble with my irq 0. well, except in at86rf230.c
<stefan_schmidt>
wpwrak: hmm, let me check, moment
<wpwrak>
or perhaps we're talking about different frameworks :)
<stefan_schmidt>
gpio_request
<stefan_schmidt>
not alloc
<stefan_schmidt>
not sure its also used on mips and if it may differ there
<wpwrak>
i think i found the source of my memory corruption. it's packets with a bad PHR (> 127)
<stefan_schmidt>
PHR?
<wpwrak>
now, if i throw them away and politely report back the problem, the whole thing hangs. hmm. more investigation needed. at least only the driver is dead, not the entire machine.
<wpwrak>
frame length
<stefan_schmidt>
wpwrak: (memory) It was funny to read this. I somehow implicit thought that with partial struct declaration all other would be 0
<stefan_schmidt>
(frame length) ah
<stefan_schmidt>
over 127 is indeed bad in ieee802154 :D
<wpwrak>
and the 128 bytes skb hates it too
<stefan_schmidt>
wpwrak: (spi master driver) How would we integrate this with atusb? Mapping the spi calls to ATUSB_REG_WRITE, etc?
<stefan_schmidt>
(skb) And I can fully understand that :)
<wpwrak>
or ATUSB_SPI_...
<stefan_schmidt>
hmm
<wpwrak>
see the dev_dbg statements in the classificator
<stefan_schmidt>
wpwrak: is there a list with available firmware commands? (I'm on latest here)
<wpwrak>
atusb/fw/include/atusb/ep0.h
<stefan_schmidt>
ah, read the f*cking source, luke
<wpwrak>
aye ;-)
<wpwrak>
new error handling, new luck ... let's see how long until the first garbled packet this time
<stefan_schmidt>
wpwrak: greetings from Jan (shoragan)
<wpwrak>
thanks ! greetings, too ! :)
<wpwrak>
japan has a funny extra wlan channel. channel number is 14, but it's 2.4 times the usual channel spacing from channel 13
<stefan_schmidt>
wpwrak: there is even more funny things about the wifi channels
<stefan_schmidt>
wpwrak: at one linux kongress, if have only been at one, they had the wifi on channel 13 IIRC
<stefan_schmidt>
and my driver did think he was in US and used the smallest amount of channels...
<stefan_schmidt>
which did not include 13...
<wpwrak>
correct. only 11 channels there :)
<stefan_schmidt>
_after_ the kongress I had a patch for it :)
<wpwrak>
i wonder if i should color-code the critters for us/eu ...
<wpwrak>
congresses are usually very fertile grounds for fixed for this sort of minor annoyances :)
<wpwrak>
monday i should get my set of atben/atusb boards as well. finally, i'll have atusbs with a working reset line ;-)
<stefan_schmidt>
yay
<stefan_schmidt>
puts in some single malt whisky and starts coding
<wpwrak>
interesting programming fuel :)
<stefan_schmidt>
wpwrak: normally its club mate (the icetea mate)
<stefan_schmidt>
Just remembered I have some left
<wpwrak>
me, diet coke for a nice boost. else, tea. well, last night is was about a liter of coffee ... today was jittery
<stefan_schmidt>
I don't like the taste of coffee.
<wpwrak>
i think that's part of the effect :)
<stefan_schmidt>
heh
<wpwrak>
well, it was instant cappuccino. so the first half liter or so went down nicely.
<stefan_schmidt>
RichardSharpe: I would start on some work work with atusb now. based on wpwrak spi master driver.
<stefan_schmidt>
RichardSharpe: Any conflicts with this on your side?
<wpwrak>
ah, i haven't mentioned the dark side yet
<wpwrak>
for interrupt synchronization, i think we need to enqueue an URB to read, then wait for the maximum time within which it would get serviced
<stefan_schmidt>
wpwrak: you alway wait with this until I start...
<wpwrak>
(this will get more predictable when switching to an interrupt EP. for now, 10 ms seems to be a good value.)
<stefan_schmidt>
not sure I really will hit irqs tonight
<wpwrak>
now, the interrupt synchronization would have to be triggered by detecting writes to TRX_STATE
<stefan_schmidt>
would be happy to have some basic skeleton running for spi read and write
<wpwrak>
so the driver would have to decode some of the requests
<wpwrak>
yeah, with spi read/write, you can already make it through the chip identification
<wpwrak>
and you'll also need reset
<stefan_schmidt>
and tx should not involve any sending as well, right?
<wpwrak>
haven't hacked this into spi_atben yet
<wpwrak>
tx ?
<stefan_schmidt>
transmit
<wpwrak>
why would transmit not involve any sending ?
<wpwrak>
how much single malt did you have left ? ;-)
<stefan_schmidt>
huh, you lost me
<stefan_schmidt>
transmit would not involve any irq
<wpwrak>
ah ! well, there's an interrupt at the end of it
<wpwrak>
TRX_END fires when a packet has been received and when a packet has been sent
<stefan_schmidt>
yeah, sure, but I can send without caring for it now :)
<wpwrak>
yes, but at86rf230.c will not be very happy when it doesn't see the interrupt :)
<stefan_schmidt>
I'm not here to make at86rf230.c happy, hmm, atcualy I am ;)
<wpwrak>
do not ask what at86rf230 can do for you - ask what you can do for at86rf230 ! ;-)