| 00:04:05 | other | Freeing init memory: 68K |
| 00:04:06 | other | Waiting for chip to read, status = 4 |
| 00:04:10 | other | ^^ any idea what that is? |
| 00:04:53 | SpaceCoaster | debug, I guess, I get status = 7 too |
| 00:12:01 | other | interesting after a handful of power cycles |
| 00:12:03 | other | the lcd works |
| 00:37:51 | RedBaron | Yeesh. I touched a header that must be included in every single microwindows .c file. |
| 00:42:45 | Aelhaz | other: that's jffs2 clearing unused blocks |
| 00:46:02 | RedBaron | Hmm...managed to hose the keyboard handler in microwindows. Whee. |
| 01:47:46 | RedBaron | Rock on! Got the screen + and - to work! |
| 01:48:21 | RedBaron | in microwindows and tinytoe's tuxscrwm |
| 01:48:52 | RedBaron | sweet. and it wasnt even that ugly of a hack. |
| 01:48:56 | scanline | RedBaron: what do they do? |
| 01:49:29 | RedBaron | Right this second, screen+ ups contrast and screen- drops contrast. going to add a shift modifier so you can do brightness as well |
| 01:49:40 | RedBaron | Anyone know what they did in inferno? |
| 01:50:17 | Aelhaz | never tried . . |
| 01:51:06 | RedBaron | hehe. Me niether. I ran inferno for about 20 seconds...maybe. :) |
| 01:55:43 | scanline | RedBaron: how did you detect those keys in microwindows' keyboard driver? |
| 01:56:11 | RedBaron | scanline: First I hacked the kernel and added in a scancode to keycode mapping entry in the kernel table. |
| 01:56:26 | scanline | ok |
| 01:56:35 | RedBaron | scanline: Second I added in a definition into microwindows for those two new keycodes. |
| 01:57:13 | RedBaron | scanline: And third I had the keyboard handler in tuxscrwm, right where it handles the 'm' menu command, inc and dec the brightness/contrast |
| 01:57:36 | RedBaron | It just took a little bit to track the pieces down since I've never seen this code before. :) |
| 01:57:36 | scanline | neat |
| 01:58:51 | RedBaron | HRm...managed to break it somehow. |
| 02:01:40 | scanline | I wonder where GoRK is... |
| 02:02:30 | scanline | This morning I wrote a "Scribble Pad" app for PicoGUI that is similar to Microwindows' Message app, but improved |
| 02:02:44 | RedBaron | scanline: cool |
| 02:12:18 | RedBaron | Urf...sometimes the nano-X server cant get the lcd backlight to turn back on if it didnt exit cleanly the previous run. |
| 02:12:29 | RedBaron | like if I ctrl-c'd it. |
| 02:14:24 | cory | http://dailynews.yahoo.com/h/p/ap/20011011/wl/1002789017attacks_military_xent191.html |
| 02:15:11 | RedBaron | heh |
| 13:02:59 | Tangent | wonders of there's been any 5V PCMCIA action since friday |
| 13:03:13 | RedBaron | Not that I've heard of |
| 13:03:22 | Tangent | Thanks |
| 13:03:39 | RedBaron | But that doesnt neccesarily mean too much :) |
| 13:08:18 | GPSFan | Tangent: I've been working on the schematic at about 60% now, but the big news is that SpaceCoaster found the touchscreen problem. |
| 13:10:06 | RedBaron | Yah. My touchscreen now works great. |
| 13:23:55 | Tangent | Cool.. I'm gonna have to update the firmware on my Tux.. it's still on July's stuff |
| 13:25:56 | RedBaron | Guys. I'm looking for opinions here. Last night I hacked buildroot on my tuxscreen so that the screen+ and screen- keys work. I mapped them increment and decrement contrast and shift+screen+- to inc and dec brightness. Does that seem like a good thing? And do you happen to know what inferno did with those keys? I never ran inferno much. |
| 13:26:33 | Tangent | RedBaron : Sounds like a good idea to me.. I think inferno used them for Zoom+/- |
| 13:26:51 | Tangent | RedBaron : I still have inferno on one of my Tux's.. I could test for real |
| 13:27:07 | RedBaron | Tangent: Hmm. Zoom in on the windowing display? |
| 13:27:22 | Tangent | RedBaron : Make the text bigger/smaller in the phonebook etc |
| 13:27:59 | Tangent | RedBaron : Of course.. I could be maiking all this up.. let me try it for real... |
| 13:28:42 | Tangent | boots up the other phone |
| 13:29:45 | RedBaron | Tangent: Alrighty |
| 13:30:11 | Tangent | RedBaron : Hmm.. in the notpad app, the Screen+ and - keys just print garbage |
| 13:30:19 | RedBaron | Tangent: laugh |
| 13:30:23 | RedBaron | Tangent: ok |
| 13:31:56 | Tangent | Print garbage in Phone book too |
| 13:32:07 | Tangent | Guess I was thinking of my Psion :) |
| 13:32:25 | RedBaron | Tangent: *chuckle* Okay. |
| 13:33:05 | RedBaron | Tangent: Do you happen to know who I should submit this patch to? I touched the kernel, microwindows, and tinytoe. Only a few lines of code, but they were all over the place. |
| 13:33:36 | Tangent | RedBaron : Not sure, but I'd guess that Russ is largely taking care of things |
| 13:33:50 | Tangent | RedBaron : If it's not him, then I'm sure he'd know |
| 13:33:55 | RedBaron | Tangent: Alrighty. thanks |
| 13:35:02 | GPSFan | Tangent: I'v got the card detect, ready/busy, all rung out as well as most of the address/databus and reset ligic. |
| 13:35:25 | GPSFan | s/ligic/logic |
| 13:35:38 | RedBaron | GPSFan: So what is going to be neccesary to do to get 5V working? |
| 13:35:40 | Tangent | GPSFan : Excellent... I guess I should really bang the latest stuff onto my Tux then |
| 13:36:18 | Tangent | RedBaron : http://www.linear-tech.com/pdf/lt1470.pdf (a couple of these would do nicely) |
| 13:36:48 | Tangent | RedBaron : Tho' I think I can hack something similar together out of spare components that I have here |
| 13:36:49 | GPSFan | I still need to re do the PCMCIA VCC and put it on my schematic, and finish the PCMCIA control circuitry. |
| 13:37:47 | GPSFan | BTW, the 1472's are avaliable from Newak at $1.89US each ( a 1472 is 2 1470's in 1 package) |
| 13:38:13 | GPSFan | Unfortunately a $25US minimum order applies :>( |
| 13:38:19 | Tangent | I need to find a UK supplier |
| 13:38:26 | GPSFan | RS ?? |
| 13:38:52 | Tangent | Tried RS already... no PCMCIA stuff at all |
| 13:39:11 | GPSFan | There is also a Micrel part that is pin-pin for the 1470. |
| 13:40:55 | Tangent | GPSFan : I see that the 1472 takes a 12V line again.. like the MAX1602 etc |
| 13:41:25 | RedBaron | Hmm. So it will take some hardware hacking for it. Is the only difference between the original pcmcia and 5v pcmcia simply the voltage supplied? Or is there an interface difference as well? |
| 13:41:28 | GPSFan | The advantage over the Maxim parts is that both the 1470 & 1472 are SO packages of 8 & 16 pins. Easy to work with, the Maxim 1600 has LOTS of pins closer than SO. |
| 13:42:41 | GPSFan | there are interface differences between Brutus & Tux, mainly Brutus uses 2 sets of 162245 like buffers (one for each slot) whereas Tux uses one set of buffers for both slots. |
| 13:43:02 | Tangent | GPSFan : I was already sold on the LT parts... they just seemed a little more closely matched to our needs |
| 13:43:29 | GPSFan | I believe they are, and there is a second source, Micrel. |
| 13:44:48 | Tangent | OK... what's the latest bits for the Tux now? I'm still on blob 1.0.9-hack etc |
| 13:45:25 | GPSFan | Tangent: other possible problems is that in the RESET circuitry, the PCMCIA pins are pulled down instead of up (as in Brutus & Assabet) and there doesn't seem to be any provision for software reset. |
| 13:46:16 | RedBaron | Tangent: Well..the touchscreen not working on 50% of the tuxs. thats fixed. |
| 13:46:20 | Tangent | GPSFan : As long as we can spare a GPIO line for it, we can easilly rig up the reset signal |
| 13:46:29 | RedBaron | Tangent: beyond that...I dont realy know. I just got my tuxscreen. :) |
| 13:46:55 | Tangent | Is this the latest? http://tuxscreen.net/download/v0.4/ |
| 13:47:05 | GPSFan | Tangent: there is one that is used by the unpopulated connector, but the direction is in vs. out. |
| 13:47:20 | RedBaron | Tangent: get the cvs buildroot and build that to get the touchscreen patch. but .4 is close to the latest. |
| 13:48:02 | Tangent | RedBaron : OK.. I'd rather do the CVS method... Is there a page with the details/instruction? or am I just gonna have to bug you? |
| 13:48:04 | Tangent | :) |
| 13:48:33 | RedBaron | Tangent: *chuckle* Feel free to bug me. There is a readme in it that explains pretty well how to do it. Have you built a buildroot yet? |
| 13:48:33 | Tangent | GPSFan : Sorry.. lost me there... Reset pin on the connector is in instead of out? or spare GPIO line? |
| 13:49:15 | Tangent | RedBaron : No.. not so far... as I say, I haven't actually touched my Tuxscreen since July... when the kerenel was still having issues with booting etc... |
| 13:49:29 | GPSFan | Tangent: the "spare GPio pin is in instead of out, but that's not really a big deal, there are a bunch of spare gates too. |
| 13:50:14 | Tangent | GPSFan : Hell.. .we could do a simle address decode and use a high bit of memory for the reset signal if push really came to shove |
| 13:51:54 | RedBaron | Tangent: Okay. The buildroot-tux is on the tuxscreen sourceforge project. You just have to have the arm toolchain installed. And make sure you have wget installed. The buildroot uses wget to get a lot of different packages. |
| 13:52:13 | RedBaron | Tangent: then type 'make' and wait a bit. :) |
| 13:52:15 | GPSFan | Tangent: yes, but probably won't be neccessary, GP23 is undefined by the .h file I saw, and anyway itis driven by some signal from the unpopulated connector. Manufacturing test?? |
| 13:52:41 | Tangent | GPSFan : We've also got the TX bit on the IRDA port free |
| 13:53:01 | Tangent | or I assume so anyhow |
| 13:53:06 | Tangent | since we're receive only. |
| 13:53:28 | Tangent | RedBaron : Yeah.. I should already have all that stuff installed... |
| 13:53:35 | RedBaron | Tangent: *nod* |
| 13:55:33 | GPSFan | Tangent: the card detect logic and socket select logic uses lots of gates, znd I don't know if I've got it all rung out yet. I should be able to post a prelinary schematic (of what I'vd got) this evening. |
| 13:56:03 | Tangent | GPSFan : If you post it, I'll verify it on my Tux here... |
| 13:56:11 | GPSFan | k |
| 13:59:41 | Tangent | What's the latest blob? |
| 13:59:43 | RedBaron | Do either of you know why the power supply for the tux has three seperate +3.3v lines? and corresponding ground lines. I'd guess it would be to keep noise from different parts of the tux. |
| 14:00:13 | SpaceCoaster | RedBaron: have you submitted your patch yet? |
| 14:00:33 | GPSFan | Current carrying capacity of the connector pins ie. to reduce IR losses. |
| 14:00:33 | RedBaron | SpaceCoaster: Was just writing up an email to Russ. |
| 14:00:54 | Tangent | RedBaron : There's certianly only one 3.3V regulator circuit in the PSU |
| 14:01:27 | RedBaron | GPSFan: Ah. okay. So does the label on the PSU mean 1.25A per 3.3v pin? or total? |
| 14:01:47 | GPSFan | Probably only 1.25A total. |
| 14:02:27 | RedBaron | *nod* I'm interested in making my tux portable. I havent gotten around to dinking with the power supply and checking current draw. |
| 14:02:36 | SpaceCoaster | aahhh, I have an idea in the same area, the backlight power is controlled by an ioctl, but the sa1100fb.c has a standard way of doing it. Done this way it works with X etc. |
| 14:02:39 | Tangent | Hrm.. the readme for the CVS blob says 'DO NOT USE' |
| 14:03:08 | RedBaron | Tangent: I used the v0.4 blob. |
| 14:03:17 | GPSFan | RedBaron: the power supply rating on the PS unit is what the supply can safely deliver, not neccessarily what the Tux will draw. |
| 14:03:19 | Tangent | RedBaron : Thanks |
| 14:03:31 | RedBaron | Tangent: probably the safest since its a rather critical part of the boot chain. :) |
| 14:03:38 | kram | has returned. |
| 14:03:53 | RedBaron | GPSFan: Yah. I was assuming the tux would draw less. Specialy if the lcd was turned off. |
| 14:04:56 | GPSFan | RedBaron: usually the LCD backlight is the most power hungry and least efficient part in the box. |
| 14:05:30 | RedBaron | GPSFan: Okay. I see that the backlight can be turned off by software. Do you know of any other peripherals that can be turned off by software? |
| 14:06:17 | GPSFan | RedBaron: do you need the DSP? if not unsolder the RF shield and unplug the Wheaties module. |
| 14:07:08 | RedBaron | GPSFan: Nope. I dont care about the dsp. Cool. didnt know that was unpluggable. |
| 14:09:32 | Tangent | Ah.. cool.. new blob defaults to 115200 |
| 14:10:51 | RedBaron | Yes |
| 14:11:35 | GPSFan | RedBaron: peek under the bottom of the RF shield and you will see a connector on the left. |
| 14:12:05 | RedBaron | GPSFan: Alrighty |
| 14:12:19 | RedBaron | opens up his tux to look |
| 14:13:48 | kram | is away - Not here right now, sorry... - Your msgs will be saved. |
| 14:16:23 | RedBaron | GPSFan: Did the lucent dsp do anything other than plain DSP work for the phone line? |
| 14:18:08 | GPSFan | RedBaron: don't know, but I do know tha phone audio goes thru it, there is no analog phone inside the Tux. DTMF too. |
| 14:19:30 | RedBaron | GPSFan: Crap. Didnt realize that 4 line connector for the touchscreen was simply a wire that fed into a clamp like connector. Now I lost the orientation. Do you know how thats supposed to be lined up? I'm guessing its the touch screen lines. |
| 14:21:06 | GPSFan | RedBaron: Oops, I believe that the touch screen connector is symetrical, and if you put it in backwards the TS may be backwards & upside down, no harm though. |
| 14:21:32 | RedBaron | GPSFan: Hmm..ok |
| 14:21:41 | SpaceCoaster | GPSFan: aahh, that would make sense |
| 14:22:02 | GPSFan | RedBaron: Or it won't work at all if there are only contacts for one side of the film. |
| 14:22:06 | RedBaron | SpaceCoaster: How is that? |
| 14:22:35 | RedBaron | GPSFan: True. it is only one sided on the film |
| 14:22:38 | RedBaron | GPSFan: Cool. |
| 14:22:52 | SpaceCoaster | RedBaron: well I couldn't work out why "some" touchscreens are inverted |
| 14:23:58 | GPSFan | SpaceCoaster: it looks like J302 has contacts for both sides of the film, so physically reversing the film should result is reversing the TS. |
| 14:24:21 | RedBaron | GPSFan: Ah. Huh. Interesting |
| 14:24:48 | RedBaron | GPSFan: We'll..I guess I'll find out when I put my tux back together. heh. |
| 14:25:04 | GPSFan | I've got to run, the wife has lots of honey-do's outside today. ;>) |
| 14:25:16 | RedBaron | GPSFan: Seeyas laters |
| 14:25:28 | SpaceCoaster | GPSFan: see ya |
| 14:26:03 | SpaceCoaster | RedBaron: how big a case do you think your mobile tuxscreen will need? |
| 14:26:10 | Tangent | Hrm.. by buildroot failed... Can not represent SWI relocation in theis object file format |
| 14:26:17 | Tangent | s/by/my/ |
| 14:27:19 | RedBaron | SpaceCoaster: Well, I eyeballed it and it looks like the width and length of the screen on the tux will be just about right. it'll be close to that. |
| 14:27:33 | RedBaron | Tangent: Hrm ... what version of the arm toolchain do you have? |
| 14:28:36 | SpaceCoaster | RedBaron: how about just gluing a lump on the back of the screen? |
| 14:29:31 | RedBaron | SpaceCoaster: Nah. I figure I'll have the screen on top, the boards underneath, and a layer of batteries under that. Thats a bit of weight to just tack on to the existing case of the screen. |
| 14:31:35 | SpaceCoaster | RedBaron: yeah but it would look nice, until you went round the back |
| 14:32:06 | RedBaron | SpaceCoaster: *nod* |
| 14:32:30 | SpaceCoaster | RedBaron: you might have inspired me! |
| 14:32:56 | Tangent | RedBaron : My toolchain is a few months old... |
| 14:33:59 | RedBaron | SpaceCoaster: :) |
| 14:35:43 | RedBaron | Tangent: I used the arm-linux-toolchain-post-2.2.13.tar.gz. Found handhelds.org. |
| 14:35:54 | SpaceCoaster | RedBaron: how big are the PCBs (too lazy to open box)? |
| 14:36:23 | RedBaron | SpaceCoaster: About as big as the screen. Which is why I say it looks like it'll work. :) |
| 14:38:18 | RedBaron | arrggh! will I never learn how to use scp correctly? Just accidnetly overwrote my screen+- patch. |
| 14:39:30 | RedBaron | Whelp. I better go before my girlfreind gets to annoyed at me. See you all. |
| 14:40:11 | Tangent | RedBaron : See you later... thanks for the help |
| 14:40:26 | RedBaron | Tangent: No problem |
| 15:58:59 | Tangent | builds with new toolchain |
| 16:00:06 | Tangent | and gets exactly the same error... Hmmph |
| 17:13:40 | Tangent | just flashes 0.4 instead... too damned lazy |
| 17:18:53 | Tangent | Cool.. my Touchscreen works :) |
| 17:20:04 | SpaceCoaster | Tangent: woohoo, amazing how many didn't |
| 17:21:48 | Tangent | The microwindows stuff is very pretty... |
| 17:21:59 | Tangent | but how do I sort the contrast out? |
| 17:22:07 | SpaceCoaster | hit 'm' |
| 17:23:52 | Tangent | Hrm... neither brightness or contrast seem to make any difference |
| 17:24:12 | GoRK | Tangent: did you apply the other patch? |
| 17:24:26 | Tangent | GoRK : No.. this is just the v0.4 files... |
| 17:24:51 | GoRK | hmm i dont think they include it... Did your touchscreen previously not work? |
| 17:25:15 | Tangent | GoRK : My TuxScreen didn't previously have framebuffer support... very old install |
| 17:25:23 | GoRK | oh |
| 17:26:03 | GoRK | are you using the buildroot stuff? |
| 17:26:10 | Tangent | I tried to do the buildroot thing, but it bombed out during the kernel compile |
| 17:26:24 | Tangent | I couldn't be bothered to fix it, so I just stuck the 0.4 stuff on instead... |
| 17:26:41 | GoRK | hmm well you have to compile your own kernel to get backlight/contrast/brightness |
| 17:26:53 | GoRK | russ has a diff on his page |
| 17:27:38 | Tangent | I'll worry about that later... I'm more concerend with getting some PCMCIA support at the mo. |
| 17:27:40 | GoRK | it wasnt included in any distribution because it caused tuxscreens that did not have touchscreens that 'worked' on linux to lock up. but that problem is fixed now also |
| 17:27:57 | Tangent | Coolness :) |
| 17:28:22 | GoRK | i'm going to be releasing a patch today that includes Linux progress patch and a kernel binary |
| 17:28:46 | SpaceCoaster | GoRK: which kernel? |
| 17:28:49 | Tangent | GoRK : Cool.. I'll happily play lab rat |
| 17:29:20 | GoRK | SpaceCoaster: the regular tuxscreen kernel. it will work with buildroot |
| 17:30:01 | SpaceCoaster | k |
| 17:30:18 | GoRK | Tangent: well it doesnt really need a lot of testing. it just does some junk to the framebuffer during boot and turns off.. if there are any bugs in it, they're sort of inconsequential at this point :) |
| 17:31:02 | GoRK | i can't seem to ge the kernel to compile with the commandline i want built into it... i changed it in the .config but it didnt work |
| 17:31:54 | GoRK | i guess blob does it |
| 17:37:04 | RedBaron | I believe that if the boot loader supplies any kind of command line, it overrides what the kernel has compiled in |
| 18:02:53 | as_ | Evnin all. |
| 18:03:04 | RedBaron | as_: Howdy |
| 18:03:14 | as_ | Hiya Baron. |
| 18:37:38 | RedBaron | Sweet. I just pulled my tuxscreen apart and it still boots and works without the phone keypad daughter board. |
| 18:38:03 | RedBaron | Now lets see how pulling out the DSP wheaties module goes. |
| 18:44:37 | Aelhaz | RedBaron: you're planning on a webpad, right? |
| 18:48:54 | RedBaron | Aelhaz: Yuppers |
| 18:49:39 | RedBaron | I figure I dont need the DSP for a webpad. |
| 18:50:26 | Aelhaz | yeah |
| 18:55:45 | RedBaron | Okay..I'll have to take my phone into work tommorow and use the facilities there to desolder the RF sheild around the DSP module. |
| 18:55:59 | RedBaron | I dont want to use my crappy cheapo solder iron on that. |
| 19:18:44 | as_ | How will your webpad connect to the net? |
| 19:18:52 | as_ | Via ethernet? |
| 19:19:02 | RedBaron | pcmcia wireless and/or wired ether. |
| 19:19:22 | RedBaron | Hmm...bye? *chuckle* |
| 19:19:26 | cory | ppp over serial! hehe |
| 19:20:39 | RedBaron | cory: hehehe. Thats an option. I'll still have the serial port. |
| 19:20:53 | as_ | Whada miss? |
| 19:21:04 | RedBaron | Not much. Cory just said I should use ppp over serial. |
| 19:21:27 | as_ | I see. |
| 19:21:59 | as_ | You could take some pictures of the DSP circuitry, I dont think we have good ones yet do we? |
| 19:22:04 | RedBaron | but yah. pcmcia ether...wired or wireless. |
| 19:22:18 | RedBaron | Sure. I'll do that tommorow when I pull off that shield. |
| 19:22:41 | RedBaron | I havent seen any pictures of that yet. |
| 19:30:41 | Aelhaz | RedBaron: it seems like the boards would take up less space if they were stacked symmetrically, which they're not in the phone |
| 19:31:20 | Aelhaz | difference of couple inches |
| 19:32:26 | RedBaron | Aelhaz: Yah. I looked at that. The only problem with that is I'd have to make a cable to connect the two boards. Then trim the connectors on the strongarm board. And then figure out some shim to make the mounting holes all fit to something. |
| 19:32:49 | Aelhaz | RedBaron: I also wonder if there might be noise concerns |
| 19:33:00 | Aelhaz | RedBaron: they used big perforated ferrite blocks as spacers |
| 19:33:01 | RedBaron | But, stacked as they are, they fit in the footprint of the screen by a few mm. Which will probably be okay. |
| 19:33:11 | Aelhaz | ah |
| 19:33:42 | RedBaron | Aelhaz: Yes. they did. they were concerned about noise. They have a big sheild between the two boards and those ferite blocks you mentioned. |
| 19:33:58 | RedBaron | Oh...and the serial port connector kind of gets in the way too. The strongarm board has a cutout where that fits. |
| 19:34:17 | RedBaron | So I'll probably just leave it as it is, and fit batteries around in the open spaces. |
| 19:34:35 | Aelhaz | makes sense |
| 19:35:08 | RedBaron | I did a quick layout and it didnt even look like I'd need a seperate layer of batteries underneath the bottom board. I was expecting to put all the batteries there. |
| 19:35:09 | RedBaron | *nod* |
| 19:36:21 | RedBaron | The more I look at this phone, the more glad I am that I bought it. :) |
| 21:32:01 | mallum | hi all |
| 23:04:36 | GoRK | ok i think i have LPP and picogui integrated somewhat into the build system... now to test |
| 23:22:36 | Aelhaz | lpp? |
| 23:25:32 | GoRK | linux progress patch .. ie graphical boot |
| 23:31:54 | Aelhaz | ah |