| |
| |
| |
|
Page: 1 2 3
Comments:
<0> thanks
<1> likewise: do you have a list of bugs preventing x86_64 target?
<2> XorA|gone: I'm trying to fix them (in a quick, non-proper way) in order to understand how many problems there are.
<2> XorA|gone: I expect the toolchain to have the most issues, not so much the packages themselves.
<1> likewise: you best bet is a x86_64 target meta bug, then start listing bugs
<2> XorA|gone: ok, thanks for that advice, I will do so.
<1> likewise: I can do test builds etc when I bored at work, but I dont physically have time to chase bugs down that I can see quickly
<2> XorA|gone: Which people where involved with the OE toolchain .bb? They are the most intertwined .bb I came across, with lot of fixes.
<1> likewise: hard to say, people tend to just dive in, Id point towards koen pb__ and RP as most probables
<3> tool chain stuff scares me :(
<4> pfff...users...
<5> I took me around a month to OE to build for sh4 working when I started work on it originally. I'd exepct x86_64 to be easier - it's probably better supported in the toolchain and glibc then sh4..
<4> (10:39:34 AM) Crofton: users ****
<1> I would guess start with x86.conf and work from there
<6> lenehan org.oe.documentation * rc9eabb30... / (1 usermanual/chapters/recipes.xml):
<6> usermanual: Updates for the recipes chapter:
<6> - Add note on ?= to the syntax section.
<6> - Fill in some details on update-alternatives.
<2> After some small fixes to linux-libc-headers, I am now stuck in the testsuite of gcc-cross. I'll continue tomorrow.
<2> good nite
<6> lenehan org.oe.documentation * rbde874d0... / (1 usermanual/chapters/recipes.xml):
<6> usermanual: Updates for the recipes chapter:
<6> - Fix up the linkend names for the update_alternatives-cl***.
<6> - Update the opening part of the volatiles section.
<7> hi there
<7> anybody there knowing how to crosscompile a kernel 2.6 for armv5tel?
<0> doch: take a look at org.openembedded.dev/packages/linux
<0> there are .bb files for various kernels there
<8> doch: Setup MACHINE and bitbake one of the .bb files Jin^eLD mentioned
<7> oh thanx, i`ll have a look at that
<7> is there a dev topleveldomain?
<7> ah ok found it
<7> ok, now i didnt find the right .bb, i was looking for a 2.6.16 for a pxa270 zaurus, do you know which ARCH i would have to give the kernel "make" for a armv5tel ?
<7> oh its just arm
<0> doch: actually you would just have to select an appropriate MACHINE in your OE configuration and build the .bb file
<9> 'night everyone
<7> ok thanx for the tips, i'll better have a deeper look at bitbake instead of tryin to build the kernel without it, n8
<10> RP: It's coming together....it's about as long as it was before but I hope it's more understandable....perhaps I need another p***
<10> RP: I mean perhaps I should take another p***...
<10> RP: I'll let you know ;-) (waiting for compile, bored)
<10> RP: ok, newer version of the patch is posted to the list
<6> koen org.oe.dev * re2629... / (1 packages/linux/linux-ezx_2.6.16.13.bb): linux-ezx: update to ezx8
<11> good morning all
<6> koen org.oe.dev * rdb7cdbcc... / (1 packages/linux/linux-ezx_2.6.16.13.bb): linux-ezx 2.6.16: also apply RPs xscale cache workaround
<12> morning psokolovsky
<13> Hi!
<6> koen org.oe.dev * ra6d3725b... / (1 packages/linux/linux-ezx/defconfig-a780): linux-ezx: update a780 defconfig
<12> koen, last evening a see (and touch) a nokia N800 ... really nice ...
<14> JustinP: I've replied with some comments. Its better each time :)
<15> Does perl build for you guys?
<14> Laibsch: It does in poky...
<15> I cannot compile it for oz-unstable
<15> RP: OK, thanks.
<16> hi, all!
<16> How could I add out-of-tree conf firectory in local.conf (to search for machine files there)?
<14> slapin_nb: Just creat conf/machines and place the file in there
<16> RP, I mean out-of-tree - where could I place it?
<14> slapin_nb: Your local.conf file is out or tree?
<14> (and it lives in a conf directory?)
<16> I have oe...... dir, and build/conf/local.conf in different paths
<14> slapin_nb: So create build/conf/machine and place the machine conf file in there
<16> thanks!
<17> mickeyl: ping
<18> Morning
<18> How do I define PREFERRED_PROVIDER_virtual/db-native?
<18> db3-native is failing to build when I'm trying bitbake gpe-image
<18> nvmd, found it in the wiki
<0> re
<15> RDEPENDS are not built, right? One has to either build them explicitly or also DEPENDS on them, correct?
<19> Laibsch: it depends
<2> LOL
<19> do not DEPEND them
<19> images/meta say to build RDEPENDS automatically
<19> iirc it is BUILD_ALL_DEPS
<19> but I'm getting rusty
<15> zecke: Well, the reason I ask is that there are a couple of RDEPENDS in ./packages/angstrom/angstrom-gpe-image.bb but they did not get built and thus compilation broke.
<15> I am looking for how to fix it. Koen?
<19> http://www.openembedded.org/bonsai/query/description/BUILD_ALL_DEPS/
<19> Laibsch: maybe these RDEPENDS can't be resolved?
<19> but don't put them into DEPENDS
<18> if bitbake wants to download something from a site that's done (in this case libxml2 from xmlsoft.org), but you've found the gz somewhere else..
<18> How can you get bb to accept that the file is already available?
<19> e.g. you have a foo.tar.gz in ${DL_DIR}
<18> yes
<19> then touch foo.tar.gz.md5 in the very same dir
<18> ah, thanks
<19> CM: is libxml2 unfetchable?
<18> So it seems
<18> Connecting to xmlsoft.org|194.199.20.115|:21... failed: Connection timed out.
<19> CM: just now? or since a couple of days?
<18> First time i tried today
<19> CM: e.g. check tomorrow and then please file a bug report
<18> It's just been for 1h now, but I'll check tomorrow
<18> zecke: thanks, compiling libxml2 now
<15> zecke: I believe you are right. It seems the names are wrong.
<10> RP: yeah, I was thinking along the same lines. Have the keyboard driver use the remote's switch state if it exist, or have the remote take over the switch state from the keyboard if loaded.
<10> RP: of course, the problem with this being a module at all is that there's no way for us to know for sure if this device is inserted in order to load the module....
<10> RP: if the keyboard's "insert" check is true then you definately have a headphone and not a remote, but if it doesn't show something inserted then you might have a remote and, as far as I've been able to figure, there's no fool-proof way to know, at any specific time, whether the remote is inserted. (i.e. on module insertion it's impossible to know if the remote is inserted or not. I'll try to look at the Sharp code again to see if anyth
<20> philippe: did you build h3800 angstrom imaghe with 2.6 kernel?
<15> zecke: ./packages/angstrom/task-angstrom-x11.bb defines the package angstrom-x11-base-depends. angstrom-gpe-image.bb DEPENDS on angstrom-x11-base, but task-angstrom-x11 needs to be built. This is not done automatically, it seems. Is task-angstrom-x11 still no candidate for DEPENDS? Or should angstrom-x11-base etc. in DEPENDS be replaced with task-angstrom-x11?
<21> What are all the different branches for? *wonder*
<19> Laibsch: just sounds like the gpe image is wrong?
<15> "the gpe image"?
<19> Laibsch: I don't know :)
<15> what do you mean? angstrom-gpe-image.bb?
<15> Yes, I suspect that there is something that is not correctly defined there.
<15> I was trying to verify this.
<19> Laibsch: if it depends angstrom-x11-base and this does not exist, then angstrom-gpe-image.bb is wrong? At least this I what I would guess
<15> Yes, I ***ume so.
<15> At least building the image fails.
<15> I will see what koen has to say.
<11> hi all
<11> likewise: *waves from oirschot*
<19> koen: you are in the US atm?
<11> zecke: no, near Eindhoven
<11> I p***ed thru Son & breughel an hour ago
<19> hehe
<2> koen: you are at the base?
<11> if all goes well I'm gonna pickup the OE server this week
<11> likewise: no, in a B&B
<6> justinp org.oe.oz354x * rb21b0528... / (6 files in 4 dirs): gizmod: add gizmod
<6> justinp org.oe.oz354x * rb9bb6df9... / (3 files in 3 dirs): gizmod: add patch to disable bmp to avoid GLIB/GTK autoconf errors
<6> justinp org.oe.oz354x * r5fbe0... / (1 packages/gizmod/gizmod_2.3.bb): gizmod: package script
<6> justinp org.oe.dev * r12dc4... / (7 files in 4 dirs): gizmod: add gizmod
<14> JustinP: It we could detect it for certain, that would make life easier
<14> JustinP: Do the values from the ADC differ when plugged in compared to when not plugged in?
<10> RP: ADC?
<10> you mean the get_remocon_raw() value?
<10> I checked for that last night and I don't think it did...I'll check again, though
<14> JustinP: I mean the value from the max1111 chip
<14> The MAX1111 is an ADC, the remote control puts a voltage onto the wire, the ADC converts to a number. Each button provides a different voltage...
<10> RP: yep, hence the problem figuring out what it means. I'll do another test.
<10> forgot for a minute what ADC stood for....
<10> RP: I grabbed the value from the ADC on module insert and it's always 255, whether or not the remote is inserted
<10> RP: trying another way
<14> JustinP: The GPIO might also make a difference...
<1> RP: I think the only thing you can tell is the difference between remote and phones with GPIO set
<1> RP: as the remote is open circuit when no buttons are pressed
<14> XorA|gone: We just need to have a way of finding if its present or not...
<1> RP: is the insert seperate from the ADC
<1> insert IRQ
<14> XorA|gone: hard to say...
<14> It looks like the HP detect and the AK interrupt are two seperate ones...
<1> Im figuring when phones are plugged in they will give an ADC reading of almost zero
<10> XorA|gone: ah....didn't think of that difference
<10> XorA|gone: I'm cleaning up the code and trying to test this right now
<10> XorA|gone: problem I'm facing is that I haven't seen a difference between remote inserted and rmeote not inserted...
<1> JustinP: I couldnt see guessing at the hardware thats there how you could
<10> yeah....
Return to
#oe
or
Go to some related
logs:
nemesis128
#math
brianetta
fuscrew
#web
hnpt.com.vn
atftpd cant bind port 69
#math
debian console 600x800
barcode reader xorg.conf
|
|