Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
<wolfspra1l>
HS codes
<wolfspra1l>
yay
<wolfspra1l>
there are so many ways to make money in the world :-)
<wolfspra1l>
it's all our ingenious inventions!
<wolfspra1l>
at least a few more people are fed, see it positively...
<kristianpaul>
hs?
hellekin has joined #qi-hardware
<wpwrak>
"harmonized system". a system of 4-10 digit codes for identifying goods for custom purposes
LunaVorax has quit [Read error: No route to host]
LunaVorax has joined #qi-hardware
rejon has joined #qi-hardware
guanucoluis1 has quit [Ping timeout: 245 seconds]
LunaVorax has quit [Ping timeout: 244 seconds]
nikescar has quit [Read error: Connection reset by peer]
nikescar has joined #qi-hardware
guanucoluis has joined #qi-hardware
xiangfu has joined #qi-hardware
xiangfu has quit [Ping timeout: 260 seconds]
nikescar has quit [Ping timeout: 240 seconds]
xiangfu has joined #qi-hardware
rejon has quit [Ping timeout: 245 seconds]
rejon has joined #qi-hardware
wolfspraul has joined #qi-hardware
wolfspra1l has quit [Ping timeout: 252 seconds]
rejon has quit [Ping timeout: 256 seconds]
emeb has left #qi-hardware [#qi-hardware]
rejon has joined #qi-hardware
guanucoluis has quit [Ping timeout: 272 seconds]
<pabs3>
meeblip.com
pabs3 has quit [Remote host closed the connection]
rejon has quit [Ping timeout: 260 seconds]
<wpwrak>
xiangfu: thanks ! nice ... your zip code is binary ;-)
<xiangfu>
I should write 0x2C :)
pabs3 has joined #qi-hardware
<wpwrak>
see if the postal workers can figure it out ;-)
rejon has joined #qi-hardware
<qi-bot>
[commit] Marcos Paulo de Souza: MIPS: JZ4770: SLCD: Use SIMPLE_DEV_PM_OPS instead of dev_pm_ops (jz-3.5) http://qi-hw.com/p/qi-kernel/c19956e
rejon has quit [Ping timeout: 260 seconds]
rejon has joined #qi-hardware
kilae has joined #qi-hardware
jluis|work has joined #qi-hardware
jekhor has joined #qi-hardware
scientes has joined #qi-hardware
Hoolxi has quit [Remote host closed the connection]
Hoolxi has joined #qi-hardware
scientes has quit [Ping timeout: 260 seconds]
rejon has quit [Ping timeout: 240 seconds]
Ornotermes has joined #qi-hardware
Hoolxi has quit [Read error: Connection timed out]
Hoolxi has joined #qi-hardware
Ayla has quit [Quit: dodo]
rejon has joined #qi-hardware
newcup has joined #qi-hardware
lindi-_ is now known as lindi-
LunaVorax has joined #qi-hardware
rejon has quit [Ping timeout: 260 seconds]
rejon has joined #qi-hardware
jekhor has quit [Ping timeout: 264 seconds]
panda|x201 has quit [Ping timeout: 264 seconds]
rejon has quit [*.net *.split]
woakas has quit [*.net *.split]
Fallenou has quit [*.net *.split]
DocScrutinizer51 has quit [*.net *.split]
woakas has joined #qi-hardware
DocScrutinizer51 has joined #qi-hardware
Fallenou has joined #qi-hardware
kuribas has joined #qi-hardware
antoniodariuh_ has joined #qi-hardware
antoniodariuh_ has quit [Quit: Leaving]
panda|x201 has joined #qi-hardware
rejon has joined #qi-hardware
rejon has quit [Ping timeout: 265 seconds]
rejon has joined #qi-hardware
xiangfu has quit [Ping timeout: 246 seconds]
panda|x201 has quit [Ping timeout: 260 seconds]
panda|x201 has joined #qi-hardware
wolfspraul has quit [Ping timeout: 244 seconds]
wolfspraul has joined #qi-hardware
kuribas has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
GNUtoo has joined #qi-hardware
LunaVorax has quit [Ping timeout: 260 seconds]
cladamw has joined #qi-hardware
aisa has joined #qi-hardware
cladamw has quit [Quit: Ex-Chat]
jluis|work has quit [Ping timeout: 245 seconds]
erikkugel has joined #qi-hardware
erikkugel has quit [Read error: Connection reset by peer]
DocScrutinizer06 has quit [Ping timeout: 252 seconds]
panda|x201 has quit [Ping timeout: 252 seconds]
paul_boddie has joined #qi-hardware
nikescar has joined #qi-hardware
<paul_boddie>
Yocto? I've heard not particularly encouraging things about OpenEmbedded, although perhaps they might also be said about OpenWrt.
<kristianpaul>
;)
nikescar has quit [Ping timeout: 272 seconds]
<paul_boddie>
It took me ages to figure out how to build just the toolchain with OpenWrt, although I doubt that it would have been slower to just disable all the packages and do a plain "make". The toolchain is surely longer to compile than the Linux kernel plus modules.
<kristianpaul>
plain make usually works
<paul_boddie>
Yes, but I thought it would save time to just build gcc and friends. That should really be an obvious make option and/or be obviously documented.
<paul_boddie>
Anyway, my extensive searching revealed an apparently huge number of embedded build systems, perhaps indicating that everyone struggles with this kind of thing.
LunaVorax has quit [Quit: Quitte]
<wpwrak>
the trick for surviving with OE is to outsource the maintenance ;-)
nikescar has joined #qi-hardware
LunaVorax has joined #qi-hardware
<paul_boddie>
I think that's what everybody is thinking. Modern capitalism at its finest! ;-)
<paul_boddie>
Still, project momentum is half the battle here: if you can have enough people doing maintenance of the different builds, there's less duplication of effort and higher reliability.
emeb has joined #qi-hardware
<paul_boddie>
It means that people like me don't have to acquaint themselves with the build system *and* the architectural and technological decisions of the GNOME project over the past n years.
rejon has quit [Ping timeout: 252 seconds]
nikescar has quit [Read error: No route to host]
erikkugel has quit [Read error: Connection reset by peer]
erikkugel has joined #qi-hardware
rejon has joined #qi-hardware
kristoffer has quit [Quit: Leaving]
nikescar has joined #qi-hardware
nikescar has quit [Ping timeout: 272 seconds]
<wpwrak>
yeah. i've seen OE hell at openmoko, where virtually everyone was exposed to it. and i've seen OE work very smoothly for the ben, where it was "outsourced" to jlime. pity jlime sort of faded away.
<paul_boddie>
Is jlime worth looking at in any sense?
<wpwrak>
it may still be the easiest way to get X11 on the ben
<paul_boddie>
I remember the OpenMoko software development situation. I once looked at MokoMakefile and was somewhat disappointed. For a start, it didn't really work like a Makefile, although you can say that none of this stuff retains the "make only what's new" properties of classic make.
<wpwrak>
but the problem is that it's no longer maintained. so it's gradually dying.
<wpwrak>
at OM, people used bitbake even to "make" the code they were developing ...
<paul_boddie>
I'm not really that interested in X11 on the Ben. It's a powerful demonstrator of running X on a screen even smaller than the original X workstations managed to do, but I doubt the practical benefits in terms of applications.
<wpwrak>
well, you have a lot of thing that "just work" with X11. you don't even have to think about why or how.
<paul_boddie>
Agreed. Configuring stuff for the framebuffer is likely to exercise code that isn't often exercised. And I suppose X11 provides the screen-sharing framework that the framebuffer doesn't, unless you can have many virtual framebuffers.
scientes has joined #qi-hardware
nikescar has joined #qi-hardware
LunaVorax has quit [Ping timeout: 264 seconds]
Ayla has joined #qi-hardware
nikescar has quit [Remote host closed the connection]
GNUtoo has quit [Quit: Program received signal SIGSEGV, Segmentation fault.]