Poky is a bunch easier to work with, (once it finally finished
compiling).  Had to study up some, but I found the LIRC recipe, and
that helped quite a bit.  I wasn't looking forward to trying to figure
recipes out to that level of detail.  I tried compiling LIRC w/ the
standard serial driver, and that worked (I could do IRSEND from the SBC
to my other box), so I have some confidence that any problems I hit will
be my own.  

I do have a few questions.  First, I'm not sure what the best way to
add in my new driver code files to POKY is, without messing with the
standard configuration.  I copied the existing LIRC to the META
directory for SqueezeOS and added it in there, and I figured out about
putting stuff in the LIRC Meta files directory to get them copied over
at compile time, but I can't get new files to be put all the way down
into the drivers directory of LIRC.  Seems like it will only go one
directory deep, and the drivers directory is 2 levels down.  I was
going to try TARing up my source, and see if it would expand that into
the right directory.  Is there a right way to do this kind of thing?

Second question is, is there a way to disable the auto firmware reload
prompting on the SBC?  I was using 7.2 (and I'll go ahead and move to
7.3 since you recommend that), and since my server is running 7.1, when
the SBC starts up, it jumps to trying to download 7.1 code, and won't
let me do anything else.  I've worked around it for the moment by
running a 7.2 server on a different box on the network, but its kind of
a pain.  And my receiver keep reloading firmware everytime I switch
between servers or go to Squeeze Network.

Also, since you're recommending moving to 7.3, what's the easiest way
to move my POKY setup from 7.2 to 7.3?

Thanks, Steve


-- 
caveman
------------------------------------------------------------------------
caveman's Profile: http://forums.slimdevices.com/member.php?userid=18237
View this thread: http://forums.slimdevices.com/showthread.php?t=49513

_______________________________________________
jive mailing list
[email protected]
http://lists.slimdevices.com/cgi-bin/mailman/listinfo/jive

Reply via email to