Log from #neuros IRC channel

yup

hrm ok

I dont know if I'd have a way to program the code in over Spy-Bi-Wire, though

yeah not sure about that

i used to work on a multithreaded os that supported msp4301611

wow

you could check it out if you want but it's kind of big

mantis.cs.colorado.edu

yeah my chip only has 2KB of program flash

[00:17]

and the compiler only does 4KB code max

[00:17]

all I want to do it control brushless DC motors. Maybe AC servo motors.

[00:17]

and read encoders and such

[00:18]

maybe some fun stuff with Nordic wireless or Zigbee or something

[00:18]

do the timers all share an interrupt vector? i thought i saw that somewhere but i can't find it now

[00:18]

woah no way you'd get zigby in 2K flash is there??

[00:19]

yeah

[00:19]

I think the Nordic wireless is supposed to be super easy

[00:19]

we had cc2420 (802.15.4) support over SPI

[00:20]

wow, not bad. yeah, I think sparkfun.com sells a nordic on a littel breakoutboard tha tI could do SPI or I2c over. maybe.

[00:20]

if I knew what I was doing

this is the platform we were using for msp430: moteiv.com

they are cheap

$130, includes a break-out section

thats a little pricey

for a manufactured board? radio and all?

although I dropped $150 on a Xilinx FPGA starter board. but it had lots of stuff on it.

[00:22]

we looked at building our own, they would have been $200+

shit i need to get going now can i answer anything else real quick for you?

nah thats ok for now

I'll be back some other time maybe

ok good luck with your project

thanks for hte help

np, see ya

[00:44]

crazy6: I have one of those mps430 USB kits. has nothing to do with this room which is about the OSD which uses DM320 platform

[00:47]

s/mps430/msp430/

[01:23]

<eigma>

anyone around who can help with a "hardware FP, software FP" problem?

<crweb>

whats a FP?

<eigma>

:P

<crweb>

no seriously...

<eigma>

floating-point?

<crweb>

maybe i'm just having a brain fart, but i can't figure out what FP would be other than frame pointer

<crweb>

ah

<eigma>

I'm talking about ld's "X.o uses hardware FP, whereas Y uses software FP"

<eigma>

never heard of it, I assume?

<crweb>

well, normally without any context FP could mean anything

[01:26]

<crweb>

floating-point i have heard of yes.

[01:26]

<crweb>

OSD uses a software FP, as the DM320CS54x is an integer only unit.

<eigma>

I'm aware

<eigma>

apparently the toolchain was compiled with hardware FP.. at least from userland's perspective

<eigma>

"libpthread.so.0 uses hardware FP, whereas sdltest uses software FP"

<eigma>

^^^ ld spits that out at me

<crweb>

ld where?

<crweb>

theres no ld on the osd firmware

<eigma>

in the toolchain???????

<crweb>

running the toolchain, and the OSD are 2 different things

<crweb>

the toolchain is compiled to run on x86

<eigma>

I never said I was running this on the OSD

<eigma>

I am cross-compiling on a PC, for the OSD (well.. the m:robe, but close enough)

<eigma>

point is, it's a DM320

<crweb>

no, the OSD is a DM320

<crweb>

the toolchain is x86

[01:30]

<crweb>

anyway. it uses nwfpe

[01:32]

<crweb>

eigma: are you using scratchbox to compile sdl?

[01:32]

<eigma>

sdl is already compiled

[01:32]

<crweb>

its an sdl problem

<eigma>

I don't see how that can be

<eigma>

none of the sdl filenames appear in the error messges

<crweb>

libpthread.so.0 uses hardware FP, whereas sdltest uses software FP

<crweb>

sdltest is an sdl file name isn't it?

<eigma>

I wrote it.. it could just as well contain just "printf"

<crweb>

?

<crweb>

you wrote ld?

* crweb is very confused

[01:35]

<crweb>

are you or are you not trying to link to sdl?

[01:35]

<eigma>

I will show you my files so there is no confusion ,ok?

<crweb>

ok

<crweb>

did you build sdl?

<eigma>

no

<crweb>

who did?

<eigma>

someone else. I have a binary (libsdl.so) compiled for the ARM and headers

<crweb>

there are many different arm's

<eigma>

it's an ARM5, compatible with the one I'm using

<crweb>

obviously not

<eigma>

you have got to be fucking kidding me

<crweb>

some arms have FP, some don't

<eigma>

are you seriously telling me you think a binary compiled with -marmv4 won't run on a -marm926ejs ?? HAHA

[01:38]

<crweb>

when you have something that uses a software or hardware fp unit, and it doesn't exist. yes.

[01:38]

<eigma>

haha

<crweb>

how can something run with a FP unit, if it doesn't exist and needs FP?

<eigma>

I have no idea how you pulled off that scratchbox development kit, but honestly, every time I've asked for your help, you've done nothing but waste my time

<crweb>

whatever

<eigma>

forget I said anything; sorry for the bother.

<crweb>

can't use hardware taht doesn't exist

<crweb>

would you like me to build you an sdl that works?

<eigma>

if it means I can link against it without installing scratchbox, then go for it

<crweb>

scratchbox has nothing to do with being linking to sdl

<eigma>

good

<crweb>

i asked if you used scratchbox because i thought you build sdl with the wrong options

[01:41]

<crweb>

but you didn't build sdl, so it didn't matter

[01:41]

<crweb>

so as you can see, i didn't persue scratchbox questions anymore

[01:41]

<eigma>

I said that I didn't want to have to use scratchbox because I know you would immediately try to shove scratchbox down my throat

[01:42]

<crweb>

all i did was ask you if you did

[01:42]

<eigma>

anyway. sorry for that comment.

[01:42]

<crweb>

if it's wrong to get bearings on a situation before exploring answers then f'ing sue me.

<crweb>

I'll see if i can get it built

<eigma>

thank you

<crweb>

the toolkit for the arm5 version might have used a different type of FP

<crweb>

its hard to tell

<eigma>

Makefile: #include <SDL.h>

<eigma>

#include <stdio.h>

<eigma>

int main(void) {

<eigma>

printf("fdsa");

<eigma>

return 0;

<eigma>

}

<eigma>

argh

<eigma>

sorry

<eigma>

Makefile: paste.scesoc.ca

<eigma>

sdltest.c: paste.scesoc.ca

[01:46]

<crweb>

btw, a non-scratvhbox toolchain package is available from deb www.limesg.com ./ for ubuntu/debian. Pretty useful if you don't want the whole svn distro on your station

[01:46]

<crweb>

could use testers

[01:46]

<eigma>

it's okay.. I just need something that works

[01:47]

<crweb>

i personally can't stand scratchbox, but its what everyone wanted

[01:47]

<eigma>

oh good

[01:48]

<crweb>

not really sure the best way to go about this. what if i give you the .so and .h's

[01:48]

<eigma>

sure

<crweb>

looks like you already have a setup that would be pretty quick to build with

<eigma>

haha

<crweb>

wait

<crweb>

$(shell sdl-config --libs)

[01:50]

<eigma>

that's just -lSDL -lpthread

[01:50]

<crweb>

ok good

[01:50]

<crweb>

and --clags?

<crweb>

odd that sdl-config doesn't have the -L paths

<eigma>

-I/usr/include/SDL -D_REENTRANT

<crweb>

see, its using your desktop's sdl-config

<crweb>

probably should hard code those instead of using sdl-config

<eigma>

tried, with no change

<eigma>

besides, what do headers have to do with link erros

<crweb>

right, just sayin

<eigma>

*errors

[01:52]

<crweb>

if sdl-config --libs gave a -L/usr/lib/SDL -lSDL then it could be pulling from your x86, but you said its not

[01:52]

<eigma>

correct

<crweb>

what version do you want?

<crweb>

1.2.11?

<eigma>

whatever

<eigma>

can you make it a static build then?

<eigma>

actually no

<eigma>

shared works better

<crweb>

i can try. sometimes oss doesn't setup nice make files for that though

[01:54]

<crweb>

ok

[01:56]

<crweb>

ah, sdl uses rpath

[01:56]

<crweb>

fun fun

[01:57]

<eigma>

AHA!

[01:57]

<eigma>

oh, how I love making the toolchain let me do dangerous things.. "-Wl,--no-warn-mismatch"

[01:57]

<crweb>

heh

<crweb>

the official fix is to recompile sdl with both FP types

<eigma>

yuck

<crweb>

--msoftfp

<eigma>

let's see if the binary runs now..

[01:59]

<eigma>

yeeeep!

[01:59]

<crweb>

good

[01:59]

<crweb>

i'd test FP just to be sure

<eigma>

ah, excellent! SDL calls work too..

<crweb>

let me know if you get NWFPE errors

<eigma>

I don't use FP anyway, so I don't really care :)

<crweb>

lots of window/drawing stuff does use fp

<crweb>

automatically

<eigma>

but.. I don't use that :) this program's only purpose is to debug the SDL support for my fb driver.. :)

<crweb>

qt gives us a large number of NWFPE errors on the FB

<eigma>

"FB"? framebuffer?

<crweb>

yes

[02:02]

<eigma>

hm.. my qt runs fine

[02:02]

<crweb>

I've been collecting the data

[02:02]

<crweb>

opie? or qtopia4 ?

[02:03]

<eigma>

opie

[02:03]

<crweb>

I'm using qt4

[02:03]

<eigma>

this image exactly --> familiar.handhelds.org

<crweb>

what version of opie is that?

<eigma>

some really ghetto one

<crweb>

pretty sure it still uses qtopia 2

<crweb>

2.11 or something like that

[02:08]

<crweb>

www.limesg.com

[02:08]

<eigma>

damn, I know I saw an an about tab somewhere.. can't find it now

[02:11]

<eigma>

anyway, there's libqte.so.2.3.10, libqpe.so.1.5.0, libopiecore2.so.1.9.4...

[02:12]

<crweb>

yeah, those might work ok

[02:12]

<crweb>

teh FP errors seem to be version to version

[02:12]

<crweb>

and 2.3 is way old

<crweb>

www.limesg.com

<crweb>

sdl 1.2.11

<crweb>

just a quick build, not much thought put into it

<eigma>

uh, it's okay.. I got it working with the binaries that are already in the distro

<eigma>

thanks though

<crweb>

if you ever get a chance to test it, give it a go

<eigma>

mmkay

<eigma>

I'd appreciate some help with debugging the FB driver now if you feel like it :P

<crweb>

I really can't

crweb: i have a more recent sdl built if you want it

<crweb>

in like +8 maybe ?

<eigma>

lol whatever

<eigma>

was mostly a joke anyway

[02:27]

eigma: you've got problems with the fb driver ? which problems ?

[02:28]

sdl tries to change resolutions when it starts up and fails ?

[02:28]

<eigma>

nero: not the IT fb driver fyi

[02:28]

<eigma>

modification of cowonfb

[02:29]

eigma: oh, you got that working ? when i tried that, it lacked the parts that actually activate the fb layer in hardware

[02:30]

can i see these modifications ?

[02:30]

<eigma>

yep, I have opie (an ancient version) running on it

<eigma>

btw, is IT planning on migrating to beyond 2.6.15 anytime soon?

hmm, i'm not sure about opie, but that fb driver might come in very handy. can you share these mods ?

<eigma>

svn.devjavu.com

and about the kernel, i don't know

<crweb>

opie has its own FB system

<crweb>

not nano-x or anything

<crweb>

well, it uses qtopia's fb

<crweb>

or an x11 if you have it

<eigma>

that, in turn, piggybacks on fbdev

<eigma>

it all comes down to /dev/fb0 either way

[02:33]

crweb: but qtopia uses the fb driver on linux

[02:33]

<crweb>

right

[02:33]

<crweb>

it all uses /dev/fb0

<eigma>

sdl is currently broken on this driver though

<crweb>

just a matter of does qtopia draw to x, or does it draw directly

<eigma>

trying to fix it

<eigma>

qtopia doesn't use x11.. afaik it has its own IPC for graphics

<crweb>

eigma: no, it uses both

<crweb>

err, either

<crweb>

it will use either

<eigma>

right

<eigma>

you're probably right

<eigma>

on my system, it's configured to go direct to the fb

<crweb>

yeah, ipaq uses pure qtopia

<eigma>

I just realized I have no idea why this driver works.. smem_start is set to an insane value

[02:36]

<eigma>

ah, no, nvm, it's fine :)

[02:36]

<eigma>

(obviously..)

[02:36]

hey folks, totally unrelated, but is there some worm around these days that generate a lot of fake delivery messages ?

[02:37]

<eigma>

nero: find anything interesting?

[02:37]

<crweb>

nerochiaro: i get about 10-15 a day like that. most of them say they come from myself

[02:37]

<crweb>

theres all sorts of stuff going around

[02:38]

<crweb>

i do see something interesting

[02:38]

<crweb>

trasp.offset transp.length

[02:38]

eigma: yeah, that fb driver you linked is definitely a step forward in respect to the one i saw some time ago. the other didn't do any of these outw calls to set hardware

<crweb>

eigma: did you download that, or are these your changes?

<eigma>

some are my changes

<crweb>

nerochiaro: i might have sent you the wrong driver

<eigma>

I didn't do much though

<eigma>

added the HW init, reformatted some stuff, modified for the mem set up of my device

eigma: where did you make these changes from ?

<eigma>

I forget.. some cowonfb.c on a forum

<crweb>

yeah, nerochiaro i think i sent you the wrong one

<crweb>

i meant to send you the one from the forum

<crweb>

iAudiophile

<eigma>

yep

<eigma>

that's the one

crweb: way to waste my time :[=]

crweb: ;)

<crweb>

i must have labeled it wrong

[02:42]

no problem, i was just joking

<crweb>

eigma: can you grab us the original and email it to tom@limesg.com

<crweb>

i can't find my login to iaudiophile

<eigma>

it's not on iaudiophile anymore?

<eigma>

www.bugmenot.com

[02:45]

the weird thing is there's a third cowon fb i've seen floating around that it's not the one eigma linked right now, neither the "empty" one that crweb sent me. it had some extra ioctls too, but i can't recall where i did see it either

[02:46]

i was getting fed up with this fb thing some time ago so i kinda threw it in a corner and forgot

[02:46]

<crweb>

it says "see attached" but its not attached

[02:47]

<crweb>

ah, think i might have it now

[02:47]

<crweb>

I was in the archive

[02:47]

<crweb>

you have to be on the real site

[02:48]

<eigma>

you got cowonfb.c or you still need the original iaudiophile version?

[02:48]

if you have it, i'd like to see that too

[02:50]

<eigma>

sure, 1 sec

[02:50]

<crweb>

got it

[02:50]

<crweb>

nerochiaro: looks like they might have a real usb driver too

[02:51]

<eigma>

who? me?

[02:51]

<crweb>

no, that forum

[02:51]

interesting

[02:52]

maybe it handles that missing piece that blocks us to do hid

[02:54]

<crweb>

nope

[02:54]

<crweb>

usb is still storage only. Hub support just adds more ports

[02:55]

which is not bad

[02:55]

<crweb>

they do have USB-Ethernet, and USB-Wireless working though

[02:56]

<eigma>

the original driver I started from is on your server crweb.. www.limesg.com

[02:56]

eigma: crweb: so anyone of you can send me the iaudiophile driver ?

hi guys

hey blackBench

hi nero

i have a qustion concerning the blackfin bf561 proc

[02:57]

are you familiar with that

[02:57]

i know noting about it

<eigma>

nero: I'm trying to DCC you the file

do you know someone who does?

eigma: thanks

<eigma>

np

<crweb>

nerochiaro: i think its the same

<crweb>

he is right www.limesg.com

<crweb>

its the one i gave you already

blackBench: the only one who i've heard talk about blackfin is user "suma" or "sumasuma"

oh oke

well thnx anyway

blackBench: no problem

<crweb>

eigma: nice work on getting it to work

eigma: which problems does it still have ?

<eigma>

the one I sent you? I don't even remember.. bad memory setup at the very least

<eigma>

the one in SVN? sdl is broken on it; haven't tested X

no, the one you have fixed and running now (the one in svn)

broken how ?

<crweb>

possibly an sdl problem no the fb?

[03:01]

<eigma>

I'm actually debugging that *right now*

[03:01]

<eigma>

so hopefully if you ask me in an hour there will be a fixed version

[03:02]

eigma: all right. i just wanted to know which kind of errors or problems it had with sdl. "broken" is a bit, hmm, generic

[03:02]

<eigma>

well.. trying to fill half the screen with white results in interlaced white/black lines

[03:02]

thanks

<eigma>

sorry.. just been trying to get to work on it for about an hour now and getting sidetracked.. just want to get it working

<crweb>

bed will now become my friend

* crweb passes out

<crweb>

night

<eigma>

cya

[03:04]

eigma: i understand that. maybe it has something to do with ntsc v/s pal mode ?

[03:04]

<eigma>

yes, that was my first thought as well.. the frame vs field mode

[03:04]

<eigma>

but haven't had a minute to investigate yet

[03:05]

ok, i'll leave you to that then. later

[03:05]

<eigma>

sorry!!

[03:05]

hey, don't worry, you don't need to apologize

[03:38]

<eigma>

aha.. "FIXME: this only works correctly for 240x320 displays"

in opie ?

<eigma>

in SDL 1.2.7

<eigma>

the qtopia video driver