#openmoko
28 December 2007
Total 5 pages. You are browsing page 4/5.
First :: Prev :: [...] [1] [2] [3] [4] [5] :: Next :: Last
16:05 <****> edit /etc/default/bluetooth iir
16:05 <****> c
16:08 <****> hmmm, is there a default pin?
16:10 <****> jeddy3: try playing with /etc/bluetooth/hcid.conf
16:12 <****> rtp, yes, that seems to it thanks
16:29 <****> what about the state of art with gta02?? The hardware isn't confirmed yet I suppose...
16:35 <****> As far as we understand it, unfortunately not.
16:38 <****> SpeedEvil: are developers at the moment working on GTA01 or GTA02??
16:40 <****> the core developers are mainly working on getting GTA02 hardware working
16:40 <****> everyone else has 01
16:44 <****> ok...so we'll see results of hardware testing on 02 very soon I hope...
16:44 <****> Well - maybe.
16:44 <****> I'd nbot expect purchasable 02's before march at the earliest.
16:45 <****> so we're talking of confirmed hardware for march??
16:45 <****> from what i hear the hardware works ok
16:46 <****> balrog-kun: really??
16:46 <****> the ui developers use gta02 too because you don't need the battery to keep it on
16:47 <****> there are some hardware bugs identified that will be addresses in the v5 or whatever revision
16:47 <****> The drivers for GTA02 are not complete enough - as I understand it - to rule out the possibility of unknown hardware bugs.
16:47 <****> And they want to get them complete enough before committing to a new hardware revision with possible buigs
16:50 <****> right, there could be more bugs in the parts that are unused yet
16:50 <****> that's at least the accelerometers and maybe some features of the glamo
16:51 <****> And damn near all of the powersaving stuff AIUI
16:52 <****> oh yes
16:57 <****> LaF0rge, ping!!
17:01 <****> balrog-kun: glamo?
17:45 <****> glamo
18:12 <****> When I do 'ipkg install -d card' I get a message that card is an invalid destination
18:12 <****> likewise /media/card
18:13 <****> Does anyone know the correct way to get ipkg to install apps to my sd card instead of flash?
18:14 <****> wurp2: newbie's wild guess : chroot ??
18:15 <****> kamathln: I'm sure that could be made to work, but it probably would be a lot of work to set up, and it probably also wouldn't work with ipkg-link
18:15 <****> I was hoping someone would know the magic word to give the -d parameter, since the wiki appears to be inaccurate on this one
18:16 <****> wurp2: ok.
18:19 <****> wurp2: iirc you have to add "dest card /media/card" to /etc/ipkg.conf
18:20 <****> and i think you need to install ipkg-link
18:28 <****> hi
18:43 <****> Can someone tell me the basics of adding the usb_host patch to the kernel ? I have moko makefile with the current revision built, now I just need to copy the patch to the right place and tell moko makefile to compile it in, how do I get the makefile to include it?
18:43 <****> Ive never done any kernel work and am overwhelmed.
18:48 <****> Marcel_M: You think I need ipkg-link before I can use the -d parameter on ipgk install?
18:49 <****> I too have done no kerne work
18:49 <****> I would think you could grep through the makefiles and find where the patch command is applied to figure out where to copy the patch and what target to call
18:49 <****> s/kerne/kernel/
18:51 <****> wurp2: sorry cant remeber just try it
18:51 <****> magellan: try: http://moko.mwester.net/uImage-2.6.22.5-moko11+svnr3238-r10.1-neo1973.bin
18:52 <****> the moko makefile documentation talks about using a quilt command to put new things in the build tree but it doesn't cover kernel patches this way, I would think there would be a similar way which didnt involve changing the makefile
18:52 <****> mwester, what is this
18:52 <****> I have tried one kernel which claims to have it built in but it didn't work
18:54 <****> mwester: how does one patch the kernel like it appears you have done?
18:56 <****> maggellan: add "file://s3c2410-usb-switch.patch;patch=1 \" into SRC_URI section of openembedded/packages/linux/linux-openmoko_2.6.22.5.bb and cp the patch to openembedded/packages/linux/linux-openmoko an do a "make rebuild-package-linux-openmoko"
18:57 <****> magellan
19:08 <****> MarcelM: how did you learn to do this
19:08 <****> is there documentation that I have missed?
19:10 <****> dunno if there is a doc
19:11 <****> Marcel_M: well it is making right now so we will see if it works
19:11 <****> great
19:12 <****> is moko makefile the way most people are coding for the neo?
19:12 <****> or toolchain
19:12 <****> let me know if you got the usb-host running ;)
19:12 <****> The documentation would be found in the OE documentation.
19:12 <****> thanks mwester!
19:14 <****> wonder if I can test this under qemu
19:15 <****> I need to see if the file "usb_mode" shows up under /sys/......../usb
19:22 <****> It's not in /sys/.../usb; it's in /sys/devices/platform/s3c2410-ohci/usb_mode
19:23 <****> oh that might work under qemu
19:24 <****> and you wouldn't need a special powered hub :p
19:24 <****> actually it should work with an unpatched kernel
19:25 <****> it didn't work with the unpatched kernel
19:28 * balrog-kun boots up
19:28 <****> well usb_mode is now in /sys/devices/platform/s3c2410-ohci/ as it should be while under qemu
19:29 <****> openmoko: andrew * r3750 /trunk/src/host/qemu-neo1973/hw/neo1973.c: Preliminary LIS302DL accelerometers in the GTA02F.
19:29 <****> now I should just have to send it to the device
19:30 <****> thanks mwester, balrog and Marcel
19:31 <****> with an unpatched kernel i have no usb_mode file in there but ohci works and you can attach devices to it
19:32 <****> you modprobe ohci?
19:34 <****> i use a non-modular kernel normally
19:34 <****> Umm.
19:34 * SpeedEvil understood that there was no way for the hardware to do that.
19:35 <****> as it can't automagically switch from device to host mode.
19:35 <****> on the real hardware i think you're right, i was talking about qemu, sorry if i was unclear
19:36 <****> in qemu it can work in both modes at the same time because the two usb sockets are not melded into one
19:36 <****> Oh right.
19:41 <****> hi there.
19:43 <****> is there any news about GPS softwares?
19:58 <****> bedboi: the gps software is working
19:59 <****> do you mean the driver, or some gps navigation gui, or what?
20:04 <****> The binary driver has been released.
20:04 <****> and 'works'.
20:10 <****> why the 's?
20:12 <****> Unless it's a newer version then the internal one, it's... well... it could be better. ;)
20:13 <****> I guess all I care about is that it feeds me timestamps & lat/longs
20:13 <****> and it does that
20:14 <****> Well, if you don't move, it always gices the same coords. ;)
20:14 <****> (which sounds right, but is wrong for gps)
20:16 <****> hmm
20:16 <****> I can see that there should be variation for error
20:17 <****> but what other variation should there be?
20:21 <****> Exactly the variation due to error. And that's basicly missing.
20:22 <****> So, once it gets a fix for a location, it just doesn't update from the satellites again until you move?
20:23 <****> Basicly yes.
Total 5 pages. You are browsing page 4/5.
First :: Prev :: [...] [1] [2] [3] [4] [5] :: Next :: Last