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
<wolfspraul>
I regret a little that we stopped working on the atben/atusb casing
<wolfspraul>
that asks for resurrection :-)
<wolfspraul>
I just want to embed the whole thing in a blob of epoxy or so. or a transparent plastic/glue, then you can still see the innards. it should not deteriorate the rf performance though.
<xiangfu>
kyak, this build is for release
<kyak>
wolfspraul: having atusb upstream would be so much nicer than a casing!
<xiangfu>
downloading...
<kyak>
xiangfu: yea, this looks good for release.. most fallouts have been fixed
<xiangfu>
kyak, Hi. since you have the directvnc. do you have the Makefile already? I would like try directvnc here.
<kyak>
yes, i got the Makefile
<kyak>
should i commit or rather upload it somewhere? it builds and runs, but the screen is mangled
<xiangfu>
kyak, do you think if a normal openwrt router can running a vnc server?
<xiangfu>
kyak, commit is better.
<xiangfu>
kyak, it builds and runs. better then those @BROKEN packages. :-)
xwalk has joined #qi-hardware
<kyak>
xiangfu: i didn't see any vnc servers ported to openwrt so far.. i also think that X11 is a requirement
<kyak>
which may be problematic for routers
<xiangfu>
ok.
<xiangfu>
just asking.
<xiangfu>
if there is vnc server running on openwrt router. then Ben Nanonote can be used as 'Monitor' :-)
<wolfspraul>
kyak: what can we do? [atusb upstream]
<wolfspraul>
let's break it down into smaller tasks
<wolfspraul>
don't underestimate the casing though, I think the current bare-pcb makes the boards essentially unusable, confining them to a lab-only developer desk
<wolfspraul>
every time I even carry them around I have to take special precautions
jekhor has joined #qi-hardware
<kyak>
wolfspraul: ressurect the atusb software development :) i might be mistaken, but i think it is currently in a half-tested stage, and not able to compile as kernel module (only monolitically).. when it's nice and clean and working and tested, then it perhaps can be accepted by upstream
<kyak>
and helping with atusb driver development is beyond my limits/knowledge.. so i could only help by testing
<wolfspraul>
yes, ok. let's see.
<wolfspraul>
my use case here would probably be that I have an atusb in an openwrt-based router, and atben in the Ben
<wolfspraul>
(for networking)
<wolfspraul>
that should be super easy to setup and get to work
<wolfspraul>
*should* :-)
<wolfspraul>
agreed? is that the use case we are targeting?
<kyak>
yeah, putting atusb in openwrt router is the use case.. putting atusb in a laptop from time to time is also a use case
<kyak>
the latest commit in ben-wpan-stefan is from 25 Sep 2011. .this is the problem
<wolfspraul>
that's probably a little harder to achieve initially, so I'd rather target openwrt on the other side first
<wolfspraul>
sure, it's, let's say, "on hold" :-)
<kyak>
so you mean, upstream it to openwrt, then perhaps it will find its way to upstream kernel.. sounds good
<wolfspraul>
not 'perhaps', but yes
<kyak>
ok, 'yes' :)
<wolfspraul>
I am thinking about the shortest path to a practical use case
<wolfspraul>
I want to use this thing
<wolfspraul>
NOW!
<wolfspraul>
:-)
<wolfspraul>
(other than looking at it, which is a start but not enough :-))
<wolfspraul>
and like I said I think I also want to experiment with some casing
<wolfspraul>
probably in the form of an epoxy or glue blob
<wolfspraul>
yes it takes away 'hackability', but what exactly would one want to do?
<wolfspraul>
so it makes more sense to document some good materials and how to exactly get it sealed, and impact on RF performance
<xiangfu>
kyak, I try to disable it under './configure'
<xiangfu>
re-generate the rootfs now.
<kyak>
argh
<wolfspraul>
don't worry, be happy
<kyak>
maybe just add faad2 to rootfs?
<wolfspraul>
kyak: have you found any time to play with your milkymist board?
<xiangfu>
kyak, it's patent package.
<kyak>
really? oh..
<xiangfu>
it's for AAC. mpeg-4
<kyak>
wolfspraul: not yet really.. but it's on my desk in front of me, so i won't forget :) just need some time
<xiangfu>
kyak, how to find out the ./configure option. ./configure --help give me nothing .
<kyak>
lemme have a look..
<wolfspraul>
excellent!
<wolfspraul>
the fpga is really a new angle/dimension to think of, so having it there for a while is good
<kyak>
xiangfu: --disable-faad should do the trick
<kyak>
i think this can be put into CONFIGURE_ARGS under the else for CONFIG_BUILD_PATENTED
pabs3 has joined #qi-hardware
DocScrutinizer has joined #qi-hardware
<xiangfu>
kyak, v
<xiangfu>
unrecognized options: --disable-faad
<xiangfu>
kyak, easy way is just './scripts/feeds uninstall faad2' :)
xiangfu has joined #qi-hardware
xwalk has joined #qi-hardware
<xwalk>
Can anyone assist me in the process of hooking up the Ben Nanonote to a Fedora Machine through usb? I can ssh into the Nanonote no problem, but I can't seem to get a ping sent from the Nanonote to a web address (e.g. google.com).
<kyak>
xiangfu: some package pulls that faad2 as a dependency, i guess
<kyak>
it seems that CONFIG_ALL makes it so that all packages are built; but only those packages not depending on BUILD_PATENTED are actually installed (i.e. actual ipk created).
<kyak>
by looking into build log i see that libfaad2 is built, but no ipk is created with "WARNING: skipping libfaad2 -- package not selected"
<kyak>
this is pretty strange.. i would say that BUILD_PATENTED must be stronger than CONFIG_ALL
<xiangfu>
make sense.
<xiangfu>
report bug again :)
<kyak>
so we need to disable shit very explicitely..
<kyak>
there are other packages that exhibit the same behaviour
<kyak>
ah...
<kyak>
i think i get it now
<kyak>
package pianobar has libfaad2 as PKG_BUILD_DEPENDS
<xiangfu>
so BUILD_PATENTED must be stronger than PKG_BUILD_DEPENDS and all others.
<kyak>
indeed
<kyak>
the problem in this particular case is that the package pianobar provides several packages, like 'pianobar' and 'libpiano'; and only 'pianobar' depends on libfaad2, but 'libpiano' doesn't depend on anything patented, so it gets build. And it leads to building of packages in PKG_BUILD_DEPENDS, which has faad2
<kyak>
in principal, this particular package is just poorly packaged
<kyak>
but there might be more packages like that
<kyak>
it could also mean that some other ipk's might require patented libraries as well, because they were present at build time, but (luckily) ipk's for these libraries are not built anyway
<kyak>
so we are not limited to mplayer problem
<xiangfu>
true.
<xiangfu>
kyak, please report a bug to upstream since you already dig such information
<wolfspraul>
I think dependency issues are potentially and in reality infinite. so I would try to clean them up carefully on an as-needed basis
<kyak>
ok..
<wolfspraul>
rather than trying to fix "them all", which must be the ultimate job for sysiphos
<wolfspraul>
but little by little we can make the dependencies both more accurate and flexible at the same time, sure
<cladamw>
xiangfu, nice now, you can back up me. ;-)
Ayla has joined #qi-hardware
jekhor has joined #qi-hardware
<DocScrutinizer>
tsunami warning cancelled
<wpwrak>
DocScrutinizer: in nuernberg ? that must be a big one
<DocScrutinizer>
bwahaha
<DocScrutinizer>
I raely spam IRC with nuernberg local news
<wpwrak>
so it's a global tsunami ? even scarier
<DocScrutinizer>
at least not the "global" channels of IRC
<DocScrutinizer>
nah, only indian ocean, like 2004
<DocScrutinizer>
so 'only' a few millions affected
<DocScrutinizer>
not exactly *global*
<DocScrutinizer>
a global tsunami would mean either a) yellowstone exploded and took USA with it, or b) some meteorite size in km-range hit some ocean. In both cases I think you couldn't globally cancel the tsunami warning
<wpwrak>
well, sometimes meteorite trajectories get mis-calculated
<DocScrutinizer>
aftershock quake 8.1, tsunami warning still extended by 2 hours
GNUtoo has joined #qi-hardware
cladamw has joined #qi-hardware
cladamw has joined #qi-hardware
qwebirc39331 has joined #qi-hardware
<qwebirc39331>
anyway of upgrading all openwrt packages from nanonote?
<xiangfu>
qwebirc39331, Hi
<qwebirc39331>
Hi
<xiangfu>
qwebirc39331, first you needs make sure the nanonote connect to Internet: openwrt-xburst.full_system-20120409-2355
<xiangfu>
qwebirc39331, I think so far no one have tried to upgrading all packages.
<qwebirc39331>
a new image? so I hace to use usbboot instead?
<xiangfu>
usbboot is faster.
<qwebirc39331>
I was trying to use a command I saw on a website, but didn't work.
<xiangfu>
sorry. what you mean "low quality" ? leak feature?
<wolfspraul>
incomplete, buggy
<wolfspraul>
the parts I mean
<xiangfu>
ok.
<Fallenou>
kyak: not sure if X11 is required by VNC server, I've seen it working on an Android plateform without X11. Android was just using the OMAP3 framebuffer (omapfb) in /dev/graphics/fb0
<Fallenou>
so I guess there is a way of using VNC server with a framebuffer
<xiangfu>
wpwrak, adam please check the NORFlash sheet. I just finished it.
<xiangfu>
I am not sure on junction. please give some advice.
<xiangfu>
check log tomorrow.
<wpwrak>
hmm, LibDir is a bit of a problem
<wpwrak>
if you have /home/qi/kicad-libs and /home/qi/board-m1, then the components aren't found
<wpwrak>
(substitute /home/qi for anything you like)
<wpwrak>
and yes, shorting all the FLASH_{RESET*,etc.} lines together doesn't look right :)
<wpwrak>
you also picked A3 paper. does everyone around here have an A3 printer ?
<wolfspraul>
I think we should merge those styles & units things into a file in the repo, no?
<wolfspraul>
and remove it from the wiki
<wpwrak>
yes, there should be a proper manual
<wpwrak>
not sure how to deal with the current flurry of changes, though. my current plan is to wait until adam runs out of steam and then start fixing things :)
<wolfspraul>
well it's better to discuss early
<wolfspraul>
or wait until the current status has reached consensus quality level
<wpwrak>
LibDir has an easy solution. good :)
<wolfspraul>
are any of the things you see being done a waste of time and need to be redone?
<wolfspraul>
as long as we are lifting each other up that's ok. but if someone goes in a wrong direction we should notify early.
<wpwrak>
there are several font size issues
<wpwrak>
i'm also not very happy with naming negated signals FOO#
<wpwrak>
the pin number in TPxx is useless. there's only one anyway.
<wpwrak>
sheet size is probably the worst time-wasting risk
jivs_ has joined #qi-hardware
panda|x201 has joined #qi-hardware
roh has joined #qi-hardware
<roh>
re
<kyak>
Fallenou: are you sure what you've seen wasn't vnc client
<kyak>
?
Ayla has joined #qi-hardware
freespace has joined #qi-hardware
<Fallenou>
kyak: it was a VNC server running on an Android gadget
<wpwrak>
wolfspraul: btw, i couldn't build kicad bzr 3493 (pcbnew didn't link). so i bumped it to 3494.
<wolfspraul>
and that worked?
<wpwrak>
it compiled fine. there was a change in just the area where the problem appeared, which i take as a good omen. (didn't try to dig deeper)
<wolfspraul>
let me know if you need upleveling
<wolfspraul>
I think next time I can do it in 1h
<wolfspraul>
I have a simple test bench now, the uplevel steps are documented, etc.
<wpwrak>
your patches applied fine to 3494
<wpwrak>
afk for a bit
<wpwrak>
back
<wolfspraul>
it seems kicad is moving to metric here and there
<wolfspraul>
so in the modules position file for example, I changed the default (and only) to metric
<wolfspraul>
and front and back in the same file _all.pos (before it was _Front.pos and _Back.pos)
<wolfspraul>
just fyi
<wolfspraul>
I don't think we are using that anyway
<wpwrak>
the .pos file ? of yes, we're using that for fab output
<wolfspraul>
oh
<wolfspraul>
then my upleveling certainly broke that
<wolfspraul>
kicad now has a dialog with some options there, metric or inches, 'force smd', front and back in separate files or in one file
<wolfspraul>
what do you want?
<wpwrak>
right now, pos2fab (from eda-tools/fab/) assumes inches. not sure what "force smd" means. not sure whether fabs are happier with front and back split or together.
<wpwrak>
pos2fab takes the .pos file and turns it into an excel-friendly .csv table
<wolfspraul>
just tell me what you want :-)
<wolfspraul>
you can look at the dialog now, see the options there