[05:07] Feb 15 23:02:44 beagleboard NetworkManager: device_creator(): /sys/devices/platform/musb_hdrc/gadget/net/usb0: couldn't determine device driver; ignoring... [06:10] argh, so I can't use NM on the onboard usbnet. [06:11] anyway, I've set the beagleboard up to be dhcp server now, instead of client. [06:11] That's consistent with what WinMobile does, at least. === DanaG1 is now known as DanaG [08:42] apw: Hey [08:43] apw: So I discussed linux-versatile on ubuntu-mobile@ [08:43] apw: See <20100211101825.GA5444@bee.dooz.org>; had a reply from ogra [08:43] apw: I think it's helpful to provide udebs and a meta [08:43] apw: Do you want a bug report? [08:43] or two rather [08:46] bug report yes please [08:49] apw: lp #522516 and lp #522515 [08:49] Launchpad bug 522516 in linux-meta (Ubuntu) "linux-versatile meta (affects: 1)" [Undecided,New] https://launchpad.net/bugs/522516 [08:49] Launchpad bug 522515 in linux (Ubuntu) "linux-versatile udebs (affects: 1)" [Undecided,New] https://launchpad.net/bugs/522515 [08:50] apw: Also, just an unrelated heads up on lp #522308 which I filed and probably went under the radar when moving to 2.6.32 [08:50] Launchpad bug 522308 in linux (Ubuntu) "linux-source-2.6.32 is empty (affects: 1)" [High,New] https://launchpad.net/bugs/522308 [08:50] no i suspect i broke that when i did the abstraction simplification [09:44] hello ubuntu people [09:50] I'd like to ask about Sharp PC-Z1 Netwalker a bit [09:51] does anyone here knows about this device? [09:51] Sleep_Walker: Some people here do, yes [09:52] 1] is it based on some babbage board? [09:52] Babbage is the name of the reference design boards from freescale used for development purposes [09:52] It's based on the same SoC, but it's a different board [09:53] I see [09:53] for instance it has no NIC, one USB port, no MIC jack so it's different from the babbage boards [09:53] 2] is someone working on merging drivers to upstream Russel's kernel? [09:54] someone upstream imx51 drivers where appropriate [09:54] *upstreams [09:55] Sleep_Walker: ATM, I am not sure that any imx51 SoC based board boots with an upstream kernel, so that would need to happen first; the kernel trees are hard to merge for various reasons [09:55] * ogra doesnt know how big the portion beyond general basic mx51 stuff is though [09:56] IIRC, there were some people working on getting at least the basic boot stuff working for imx51 upstream, but that's a long way to go until we get to things like wifi or video drivers... [09:56] Sleep_Walker: it will boot with a 2.6.34, I've pushed the base mx51 code upstream [09:57] and where are these people gathered? (mailing list, irc, forum...) [09:57] but there's a LOT to be done, in case you're looking to help [09:57] amitk: yeah, I had something like that in my mind... [09:58] (if there will be time) [09:58] I noticed your patches so I was curious [09:58] unfortunately I don't know much about Netwalker's HW [09:59] only that I was able to read from sources and from running system [09:59] Sleep_Walker: Just hang out on #ubuntu-kernel if you need some help and on linux-arm-kernel otherwise [09:59] amitk: You pushed the Netwalker code upstream? [09:59] persia: Babbage base code (serial port, timers, clocks) [10:00] Ah. Do you know if anyone is pushing the Netwalker patches? [10:00] lool: There's actually two USB ports : one full-size, one mini. [10:01] is it OTG capable? [10:01] and can that be charged from USB? [10:01] persia: Netwalker is the pegatron stuff? [10:01] amitk: Not at all (why does everyone think this?) [10:02] heh [10:02] persia: too many codenames... [10:02] Sleep_Walker: The mini port looks like an OTG port, but I haven't tried to use it, actually. [10:02] with no context [10:03] Yeah, well. Netwalker is it's own beast. There's kernel patches for the kernel that shipped, but I haven't heard about anyone porting them to newer kernels or pushing them upstream. [10:03] persia: I tried to connect it with PC with no success [10:03] persia: Well true, I meant one full size one compared to 4 on babbage boards [10:03] persia: is there a public git tree for the sources? Who did the kernel? What company made it? [10:03] Both have mini-USB ports [10:03] Sleep_Walker: I don't believe the USB Gadget driver is included in the shipping kernel: you might need to fiddle the kernel configuration. [10:04] and that is the problem - I wasn't able to find any comunity about this device [10:04] amitk: Not git, but there's a public apt-get source repo. [10:04] (I heard the Netwalker kernel devs don't use git) [10:04] amitk: netwalker is a sharp device [10:05] Sleep_Walker: The community is almost entirely local. The device has seen very little adoption overseas. [10:05] persia: I saw some SW support but I wasn't sure about HW support [10:05] Sleep_Walker: Aside from accellerated audio/video codecs, everything seems to be open-source. [10:05] persia: and their kernel is based on freescale's SDP? [10:05] http://www.ubergizmo.com/15/archives/2009/08/sharp_netwalker_unveiled.html [10:06] amitk: I don't know precisely. When it comes to kernels, I'm just a user :) [10:06] That's not quite right. It's 10 hours JEITA, which means 5-7 depending on load. [10:07] persia: if you can point me to the source, I could have a quick look when I have some time. [10:07] Sharp just released a new "Dictionary edition" in the past couple weeks. The specs seem about the same (just different software load), but all the samples at the shop were password-locked, and I didn't want to try to hack them. [10:08] amitk: Sure. Let me dig up what I have. [10:08] * persia fusses with apt sources [10:09] amitk: If you find it's not terribly hard to get up-to-date kernels, I'll give you one :) [10:10] amitk: http://netbook-remix.archive.canonical.com/updates/pool/public/l/linux-fsl-imx51/linux-fsl-imx51_2.6.28-15.50fsl1araneo19.dsc [10:11] That's from January. I'm unsure if there's a newer one on the new "Dictionary Edition" devices. [10:11] But that's definitely enough for basic HW enablement. [10:12] psi died - sorry - did I miss something? [10:15] Sleep_Walker: I posted the URL to kernel sources for the Netwalker. Dunno if those are useful to you. [10:15] Nothing else meaningful. [10:16] persia: does it differ from the ones I get with apt-get source [10:16] or from the one provided by sharp? [10:16] Don't think you. You're getting linux-fls-imx51 2.6.28-15.50fsl1araneo19 ? [10:16] s/you/so/ [10:17] But I haven't checked the uname on the newest edition, so I don't know if there's a new kernel available from Sharp. [10:17] ....araneo18 [10:17] I don't think so [10:18] and I thought I bought finaly device for work and not to hack :b [10:19] persia: I don't see any 28-15.50 at http://netbook-remix.archive.canonical.com/updates/pool/public/l/linux/ [10:19] amitk: `dget http://netbook-remix.archive.canonical.com/updates/pool/public/l/linux-fsl-imx51/linux-fsl-imx51_2.6.28-15.50fsl1araneo19.dsc` should get you want you want. [10:20] It's in the linux-fsl-imx51 subdirectory. [10:21] ok, I'll try to create wiki page about Netwalker (sorry, but not ubuntu one) to gather informations and possible community around Netwalker [10:21] thanks for all your help [10:21] bbl from work [10:21] Sleep_Walker: Please share the URL when you get it together. [10:21] Sleep_Walker, if you create one, can you point us to it so we can at least link it from the ubuntu wiki ? [10:22] of course [10:22] I don't want to split efforts around t [10:23] persia: so it's called erdos... [10:25] I'lll put it on hackndev.com - distro neutral area :) [10:25] amitk: erdos? [10:26] persia: the board is called erdos in the kernel tree [10:26] Ah. [10:27] and from a 5s look, the patches that I pushed upstream ought to be able to boot on it (given that IO mappings are identical to babbage) [10:27] So I should be able to boot a babbage kernel? I can test with lucid if you like. [10:28] erdos is name of Netwalker's board in kernel? [10:28] persia: I don't think so, the bootloader board id needs to match [10:28] lool: That's a bootloader thing or a kernel thing? [10:28] persia: naah, it'll require a tweak or two, but the kernel should probably be 99.99% identical [10:28] Plus the board support file will try to load drivers at various I/O addresses where you might miss devices or have other ones, for instance the netwalker has builtin wifi and not babbage etc. [10:28] persia, upstream, not lucid [10:28] * persia is *not* overwriting the nice dual-boot support redboot [10:29] lool: we're talking about the upstream (minimal) babbage kernel [10:29] you can do it on kernel side [10:29] lool: wifi is through separate modules. [10:29] persia: The kernel needs to grow a new netwalker board file with the proper board id and this file needs to be tweaked to list the proper devices [10:29] amitk: I'm not sure which babbage kernel persia meant [10:29] lool: the board id is mapped to babbage [10:29] exactly [10:30] * persia was kinda hoping for the lucid babbage kernel, but will trust statements that this doesn't work (didn't work with karmic kernel) [10:30] amitk: Oh you mean netwalker uses babbage's? [10:30] MACHINE_START(MX51_BABBAGE, "SHARP PC-Z1") .phys_io = AIPS1_BASE_ADDR, .io_pg_offst = ((AIPS1_BASE_ADDR_VIRT) >> 18) & 0xfffc, [10:30] which should be fine for bringup [10:30] Hmpf [10:30] just not for all devices [10:30] lool: right [10:30] amitk: isn't this ugly? [10:30] lool, did you expect beauty ? [10:30] persia: it seems that a minimal upstream kernel would work with the babbage id then; nervermind [10:30] lool: tell me about it, they were too lazy to even get their own board id [10:30] :b [10:31] persia: I wouldn't try booting a full blown kernel though, that might blow things up [10:31] lool: As in physical damage? [10:31] I can't exclude that [10:32] persia: I think there is no danger with physical damage with the minimal kernel going upstream in 2.6.34. Since it keeps most IO pins to their defaults [10:32] and we're no where close to a full-blown kernel yet [10:32] amitk: I think persia intended to use the lucid babbage binary kernel against a netwalker [10:33] Ah. I think I'll wait then, since I use this daily as a handheld, and it also houses my lucid pbuilder environment :) [10:33] Which I fear has a small chance of being dangerous [10:33] true === Sleep-Walker is now known as Sleep_Walker [10:58] apw: Thanks for the quick fix [10:58] we get into trouble if the source is missing ... [11:26] lool: ping. for ARM softbootloader, I need to have kexec-tools available for kexec, but the package unfortunately then changes the installed system to use kexec for rebooting as well which is unfortunate. I want to split the package out so I can have kexec installed and on its own without having the restart script stuff, any ideas on how to best do that? [11:26] apw: Ah? I saw only three rbdeps in universe [11:27] NCommander: the restart stuff is disabled in Ubuntu by default [11:27] people complain when that package is empty as they percieve it contains the source, and if its empty we arn't publishing it, even though its in the the 'source' package [11:28] apw: Ah so a lot of people get it wrong, eh [11:28] yep [11:30] apw: Now you just need to find a way to make `apt-get source linux` work :) [11:30] persia, define work [11:30] apw: heh. DWIM : download the source for the source package named "linux". [11:31] Current trick is to use `apt-get --only-source source linux` [11:32] lool: hrm, that must be a recentish change. Ignore previous ping then :-) [11:32] NCommander: It's not [11:32] It might be that you used the Debian package during the sprint [11:32] lool: It still did the kexec-load in karmic. [11:32] Which was the last time I looked at this [11:33] This was disabled in June [11:34] * NCommander shrugs [11:34] lool: sorry for the noise [11:41] dyfet: ping [11:42] *yawn* [11:43] morning [11:43] Hi... wasn't sure if you'd be up [11:43] I had a question on gmp [11:44] oh I remember that... [11:44] Did you try to build the asm code for Thumb-2 in the end? [11:45] I had some trouble with coming up with a patch for configure. They reject using try_compile, and try to do everything by the gnu target architecture tags alone [11:46] Actually, I had an idea for that... you can maybe get the predefined macros out of GCC and munge that. I wrote some notes on the Thumb-2 howto wiki page. [11:46] Oh, okay, cool! I did not notice that [11:47] It was late yesterday :) [11:47] But that is kind of what I need to do for that one :) [11:48] However, if you do try to build this code for Thumb-2, we do need to check that the function symbols in the asm are properly tagged as function symbols, otherwise they would get called as ARM accidentally. [11:48] I think that the PROLOGUE() m4 macro used in the asm does this, but I didn't fully track down where it's defined. [11:49] Ah.... [11:49] great. we have 1 builder again ;) [11:49] https://edge.launchpad.net/builders [11:50] Did you have >1 or 0 builders before? [11:50] perfect timing in a3 week ;) [11:50] dmart: 0 [11:50] (I'm guessing >1) [11:50] dmart: this morning we had 0 ;) ... usually we have 7 [11:50] Oh, OK [11:50] What's the problem? [11:51] For me, lack of coffee :) [11:51] dmart: not sure. our is knows about it and are investigating. most likely the aweful pegatrons died again [11:52] Hum [11:53] * asac hopes for new build machines ;) [11:54] dyfet: To check whether a symbol is a proper Thumb code symbol, you need to use readelf -s