| 03:30.39 | *** join/#edev DrZimmerman (n=theo@77-56-242-58.dclient.hispeed.ch) |
| 04:55.47 | *** part/#edev pea (n=pea@adsl-75-58-4-163.dsl.dytnoh.sbcglobal.net) |
| 05:13.25 | *** join/#edev Redhatter (n=vk4msl@203.94.56.252) |
| 05:13.38 | *** join/#edev harpal (n=Harpal@122.169.108.195) |
| 06:42.24 | *** join/#edev mbuf (n=user@61.16.248.242) |
| 06:51.11 | *** join/#edev lyakh (n=lyakh@p57BD2B5C.dip0.t-ipconnect.de) |
| 07:06.24 | *** join/#edev boris_OmegA (n=boris@194.51.141.172) |
| 07:09.56 | *** join/#edev mbuf` (n=user@61.16.248.242) |
| 07:13.01 | *** join/#edev notadev (n=notadev@fu/coder/notadev) |
| 07:17.03 | *** join/#edev [AD]Turbo (n=turbo@host239-240-dynamic.22-79-r.retail.telecomitalia.it) |
| 07:19.12 | [AD]Turbo | hi all |
| 07:25.25 | *** join/#edev hw__ (n=hw@p578b3905.dip0.t-ipconnect.de) |
| 08:40.14 | *** join/#edev mbuf (n=user@61.16.248.242) |
| 09:35.25 | *** join/#edev steliosk (n=Stelios@athedsl-4421802.home.otenet.gr) |
| 10:11.43 | notadev | moin |
| 10:18.09 | *** join/#edev likewise (n=likewise@87.234.195.68) |
| 10:51.20 | *** join/#edev g1powermac_PB (n=g1powerm@unaffiliated/g1powermac) |
| 11:10.12 | methril | yo |
| 11:21.22 | *** join/#edev lyakh (n=lyakh@p57BD2B5C.dip0.t-ipconnect.de) |
| 11:28.52 | *** join/#edev steliosk (n=Stelios@athedsl-393567.home.otenet.gr) |
| 11:30.24 | *** join/#edev likewise (n=likewise@87.234.195.68) |
| 11:47.39 | *** join/#edev steliosk (n=Stelios@athedsl-393567.home.otenet.gr) |
| 12:51.03 | *** join/#edev g1powermac (n=g1powerm@unaffiliated/g1powermac) |
| 13:29.43 | *** join/#edev lifeeth (n=Praneeth@unaffiliated/lifeeth) |
| 13:35.25 | *** join/#edev likewise (n=likewise@87.234.195.68) |
| 13:42.31 | *** join/#edev prpplague^2 (n=dave@mail.americanmicrosystems.com) |
| 13:43.13 | *** join/#edev dfarnsworth (n=dfarnswo@65.200.49.156) |
| 13:44.07 | *** mode/#edev [+o prpplague] by ChanServ |
| 13:48.38 | prpplague | HcE: ping |
| 13:48.38 | HcE | prpplague: You sent me a contentless ping. This is a contentless pong. Please provide a bit of information about what you want and I will respond when I am around. |
| 13:50.02 | HcE | waits for additional information |
| 13:51.43 | prpplague | HcE: hey, we are getting ready to eval the avr32 for a project |
| 13:51.58 | prpplague | HcE: any current "gotchas" in the linux kernel for avr32 support |
| 13:52.01 | prpplague | HcE: ? |
| 13:52.04 | HcE | it will fit perfectly ;) |
| 13:52.20 | HcE | grab 2.6.27, it should be quite stable |
| 13:52.35 | prpplague | ahh good deal |
| 13:52.44 | prpplague | HcE: i assume there is uboot support? |
| 13:53.01 | HcE | yes, grab latest available upstream |
| 13:53.18 | HcE | I even think there is support for DataFlash and NAND flash in the master branch |
| 13:53.31 | prpplague | nice |
| 13:53.43 | prpplague | HcE: anyone doing avr32 cput modules? |
| 13:54.02 | HcE | not really, I hoped Atmel would do it |
| 13:54.19 | *** join/#edev wmat (n=wmat@208.68.89.160) |
| 13:55.06 | HcE | I guess the NGW100 is the closest you get to a CPU-module |
| 13:56.22 | prpplague | HcE: we are considering something similiar to the sledgehammer - http://www.elinux.org/SledgeHammer_Board |
| 13:58.25 | prpplague | HcE: we just got the request over the weekend, so i have to do some research on it this week(along with everything else i have to get done) |
| 13:59.25 | HcE | prpplague: what about using the Hammerhead? http://www.miromico.ch/index.php?sec=pr.hh&lang=2 |
| 14:00.44 | prpplague | HcE: that looks dandy, any idea of the cost? |
| 14:01.41 | *** join/#edev prpplague^2 (n=prpplagu@ppp-70-244-162-142.dsl.rcsntx.swbell.net) |
| 14:02.47 | HcE | prpplague: sorry, no idea, guess the FPGA will up the price a bit |
| 14:02.53 | prpplague | yea |
| 14:03.05 | prpplague | plus there will be markup |
| 14:03.13 | prpplague | just as easy to do the board ourselves |
| 14:04.19 | HcE | mmm |
| 14:04.36 | HcE | if you have good layout dudes, it is always nice to do it yourself |
| 14:04.56 | prpplague | well we are a hardware company so it is kinda what we do, hehe |
| 14:06.13 | HcE | hehe |
| 14:06.20 | HcE | and you do software? |
| 14:06.38 | prpplague | i do the board bringup and customer drivers |
| 14:06.47 | HcE | oki |
| 14:06.55 | HcE | sounds like a fun job |
| 14:07.04 | prpplague | HcE: http://www.amltd.com and http://www.tincantools.com |
| 14:07.19 | prpplague | HcE: it has it's ups and downs like anything else |
| 14:07.27 | HcE | LOL |
| 14:07.29 | HcE | tincantools |
| 14:07.32 | HcE | nice picture |
| 14:07.46 | HcE | you should have pileoftools.com as well ;) |
| 14:08.18 | prpplague | will mention that to the boss |
| 14:10.11 | prpplague | HcE: basically we were thinking something similiar to the hammer, but with more i/o |
| 14:11.20 | HcE | oki |
| 14:12.09 | prpplague | HcE: using the avr32 |
| 14:12.10 | HcE | prpplague: how would you feel like a CPU module with; bootloader flash, x MB NAND flash, x MB 32-bit SDRAM and USB connector? All other I/O routed through connectors to customers hardware. |
| 14:12.57 | prpplague | HcE: yea thats basically what were are looking at |
| 14:13.43 | HcE | prpplague: in what degree would you like to be able to choose SDRAM and NAND flash size? |
| 14:14.05 | prpplague | HcE: generally we only need one configuration |
| 14:17.22 | prpplague | HcE: min requirements would be probably 32/32 |
| 14:17.40 | HcE | ?? |
| 14:17.46 | HcE | 32 MB NAND and 32 MB SDRAM? |
| 14:17.52 | HcE | or 32 MB NOR + 32 MB SDRAM ? |
| 14:18.24 | prpplague | 32MB NAND and 32MB SDRAM |
| 14:18.33 | HcE | ok |
| 14:18.44 | *** join/#edev GPSFan (n=kenm@64.92.145.112) |
| 14:18.44 | HcE | for AP7000 you will need a NOR flash as well |
| 14:18.44 | *** mode/#edev [+o GPSFan] by ChanServ |
| 14:18.51 | HcE | (direct addressable) |
| 14:19.22 | prpplague | ahh, doesn't directly support nand booting? |
| 14:19.33 | HcE | nope |
| 14:21.43 | prpplague | no real problem with that, just means an extra chip |
| 14:22.09 | HcE | yes |
| 14:22.22 | HcE | or you could use a 32 MB NOR flash to keep everything |
| 14:22.51 | HcE | I do not know what is cheapest (small NOR + 32 MB NAND) vs. (32 MB NOR) |
| 14:23.19 | prpplague | two current issues with the nor flash, 1) it is pretty expensive, 2) you have to run alot of address/data lines on the board |
| 14:23.41 | prpplague | HcE: does the ap7000 support any other boot methods? |
| 14:24.13 | HcE | prpplague: nope, AP7000 starts executing from 0x80000000, which is wired to CS0 |
| 14:24.51 | prpplague | shame, really should have support for alternate method such as a eeprom or uart |
| 14:25.31 | HcE | next device will support that |
| 14:25.36 | prpplague | ahh |
| 14:25.43 | HcE | it has a bootrom |
| 14:25.47 | prpplague | pin compatible? |
| 14:25.52 | HcE | nope |
| 14:26.01 | prpplague | ahh |
| 14:26.03 | HcE | not a replacer, just the next step |
| 14:27.30 | prpplague | ahh ok |
| 14:37.52 | prpplague | wonders where cosmic is this morning |
| 14:38.18 | prpplague | anyone know a linux based device that is using number keypad text entry? |
| 14:42.53 | prpplague | works on a keypad driver |
| 14:59.19 | *** join/#edev chouimat (n=dieu@kde/developer/chouinard) |
| 15:02.32 | HcE | prpplague: I'll have the chance of writing one in "near" future |
| 15:05.12 | prpplague | HcE: just trying to decide on a better way of doing it |
| 15:05.24 | prpplague | HcE: we've had two in the past, but i don't like the complexity of the code |
| 15:05.42 | prpplague | HcE: too many state variables |
| 15:10.43 | HcE | oki |
| 15:10.56 | HcE | I have a keypad hardware driver, so it is easy to use |
| 15:11.02 | HcE | get interrupts and just read state |
| 15:12.54 | *** join/#edev CosmicPenguin (n=nobody@163.181.251.103) |
| 15:12.54 | *** mode/#edev [+o CosmicPenguin] by ChanServ |
| 15:15.21 | MothaWork | HcE: AP7000 doesn't support Dataflash boot like the 91SAM ARMs do? |
| 15:22.08 | *** join/#edev adyer (n=adyer@adsl-69-223-13-78.dsl.chcgil.ameritech.net) |
| 15:27.35 | prpplague | HcE: yea getting the actually keypad data isn't really a problem |
| 15:27.51 | prpplague | HcE: doing the text entry from keypad can be a little complex |
| 15:30.33 | solar | guesses this is so you can get function+5555 = L |
| 15:32.39 | prpplague | solar: yea |
| 15:32.53 | prpplague | solar: function+555 = l |
| 15:33.12 | solar | ya I thought about that after i typed it that it should be one less 5 |
| 15:33.22 | prpplague | solar: reworking the driver now |
| 15:35.24 | MothaWork | prpplague: sounds like this could probably be done using two state variables and a 2D array |
| 15:35.52 | MothaWork | one state to track function/mode, one state (2D) to track indices |
| 15:36.10 | prpplague | MothaWork: yea, that's basically what i'm looking at now |
| 15:36.41 | MothaWork | the matrix is not a part of the state machine but rather a lookup table to create the output (which technically makes it part of the machine, but has nothing to do with transitions) |
| 15:36.48 | prpplague | MothaWork: i'm redoing all the logic and timer fuctions now |
| 15:36.58 | MothaWork | prpplague: does this live in kernel land or user land? |
| 15:37.00 | prpplague | MothaWork: indeed |
| 15:37.10 | prpplague | MothaWork: this is kernel space |
| 15:37.21 | prpplague | MothaWork: i want it transparent to applications |
| 15:38.45 | MothaWork | hum, sucks having to do all that in kernel land |
| 15:39.02 | MothaWork | timer heavy stuff like that is often prone to "bad stuff" |
| 15:39.24 | MothaWork | perhaps a kernel->userspace->kernel system? Would let people replace it easily, too |
| 15:39.27 | prpplague | MothaWork: yea, but makes it easier for end developers, which is a plus for us |
| 15:40.08 | MothaWork | kernel driver for the raw input (just provide the hardware status), userspace app deals with that and comes up with the key events to synthesize, then push that back into the input layer |
| 15:40.15 | MothaWork | heck, there may already be an API for that... |
| 15:40.32 | prpplague | MothaWork: gnome/gtk has some support for that |
| 15:40.50 | MothaWork | I seem to recall reading about an API to synthesize kernel input events |
| 15:41.37 | MothaWork | I guess this doesn't really matter a lot if you can get it working stabily in kernel space and the ability to replace it isn't a big deal |
| 15:45.38 | *** join/#edev Ecco_ (n=User@LRouen-151-72-31-65.w80-13.abo.wanadoo.fr) |
| 15:45.46 | Ecco_ | Hello |
| 15:46.05 | Ecco_ | I'm a software engineer, and I'm looking for some advice on a very low-level embedded project |
| 15:46.16 | Ecco_ | (smart-card like) |
| 15:57.33 | *** join/#edev chouimat|tv (n=dieu@kde/developer/chouinard) |
| 15:59.18 | prpplague | Ecco_: running linux? |
| 15:59.34 | Ecco_ | prpplague: On some of my machines, yeah |
| 15:59.45 | Ecco_ | I'm not really interested in programming an actual smartcard though |
| 15:59.53 | Ecco_ | I'd like to build up a "custom" smart card |
| 16:00.27 | prpplague | Ecco_: any particular reason current smart cards aren't doing what you need? |
| 16:00.47 | Ecco_ | Yep :-) |
| 16:10.55 | *** join/#edev kergoth (n=kergoth@65.200.49.156) |
| 16:14.48 | *** join/#edev DrZimmerman (n=theo@77-56-236-190.dclient.hispeed.ch) |
| 16:19.34 | prpplague | ho ho hum |
| 16:19.41 | prpplague | aren't mondays grand? |
| 16:23.23 | chouimat|tv | morning |
| 16:43.10 | *** join/#edev chouimat (n=dieu@kde/developer/chouinard) |
| 16:51.49 | *** join/#edev steliosk (n=Stelios@79.107.27.111) |
| 17:22.34 | *** join/#edev chouimat (n=dieu@kde/developer/chouinard) |
| 17:28.47 | *** join/#edev chouimat (n=dieu@kde/developer/chouinard) |
| 17:31.08 | prpplague | ho ho freaking ho |
| 17:31.18 | prpplague | tries to grind through the load of work |
| 17:36.44 | ds2 | work pile above eye ball level yet? |
| 17:37.36 | g1powermac | hmm, the pile of stuff on my desk is approaching eye ball level. . . |
| 17:38.26 | ds2 | send in the bobcat! |
| 17:39.09 | g1powermac | hehe |
| 17:43.24 | prpplague | ds2: i prefer lighter fluid and matches for cleaning up the desk |
| 17:43.54 | prpplague | kernel oops, too much going on inside a timer functions |
| 17:47.05 | ds2 | prpplague: fire marshall tends to frown upon that ;) |
| 17:48.31 | *** join/#edev lyakh (n=lyakh@p57BD2B5C.dip0.t-ipconnect.de) |
| 17:58.32 | solar | uses canned air to clean desk. Everything that falls off was/is trash |
| 17:58.41 | agaffney | heh |
| 18:08.46 | ds2 | sure it is still air? not propane? |
| 18:09.11 | ds2 | damn it i can't do banking today |
| 18:11.16 | *** join/#edev zachb (n=zachb@c-71-192-250-122.hsd1.ma.comcast.net) |
| 18:11.27 | HcE | prpplague: aha, typically implement a lookup table or similar, can be tricky indeed because of the user is able to hook up whatever keys he wants :/ |
| 18:11.49 | HcE | MothaWork: not AP700X, but AP7200 will support DataFlash boot IIRC |
| 18:12.00 | HcE | MothaWork: AP700X does not have a bootrom |
| 18:12.19 | prpplague | HcE: actually this is a fixed keyboard: http://www.elinux.org/M8050 |
| 18:13.14 | HcE | prpplague: aha, my hardware module is a generic 8x8 (IIRC) keypad decoder |
| 18:13.32 | MothaWork | HcE: ah, that makes sense then. I take it the 7200s will also support NAND? |
| 18:13.44 | MothaWork | NAND boot, that is |
| 18:13.55 | prpplague | HcE: yea, this is complex due to the fact that it needs to generate text in a similiar way as a cell phone |
| 18:13.55 | MothaWork | "it's just software" :) |
| 18:14.06 | HcE | MothaWork: hmmm, not sure, do not remember. But NAND booting is not recommended IMHO |
| 18:14.21 | MothaWork | sounds like the 91SAM9xxx stuff |
| 18:14.27 | HcE | it is not ;) |
| 18:14.35 | MothaWork | NAND boot doesn't work on all revisions, and even when it is supported is apparently kinda flaky |
| 18:14.41 | ds2 | prpplague: you running X? |
| 18:15.04 | prpplague | ds2: yea |
| 18:15.05 | HcE | MothaWork: well, the coming NAND devices does not guarantee block 0, so it will be useless in the future :( |
| 18:15.09 | MothaWork | Atmel has some good hardware, but it's often quirky |
| 18:15.17 | prpplague | ds2: or atleast the base model will be |
| 18:15.22 | ds2 | prpplague: why not have the X side take care of the T9 capabilities? |
| 18:15.27 | HcE | MothaWork: AP7200 also has a USB rescue shell ;) |
| 18:15.27 | MothaWork | HcE: gah... They're thinking of nothing but mass storage devices with that move |
| 18:15.39 | HcE | MothaWork: I know, it sucks :/ |
| 18:15.43 | MothaWork | our current NAND parts do guarantee block 0, at least |
| 18:15.51 | HcE | mmm, most SLC does these days |
| 18:15.59 | MothaWork | even some of the MLC does |
| 18:16.04 | HcE | but everybody is moving towards MLC... |
| 18:16.10 | prpplague | ds2: because i can't guarrantee that the device will always be running x |
| 18:16.19 | ds2 | oh |
| 18:16.21 | MothaWork | IIRC, the Micron 29F8G08 guarantees block 0, and it's MLC |
| 18:16.36 | ds2 | your not completely embedded, embedded device delemia :/ |
| 18:17.08 | prpplague | ds2: remember we sell these to VARs/ISVs that develop their own applications |
| 18:17.10 | MothaWork | ds2: well, this is the "platform" dilemma that hardware makers can get into |
| 18:17.28 | HcE | MothaWork: that is nice, I hope some vendors keeps embedded devices in their mind when they design new flash devices. But I guess SSD is where the big bucks will be in a couple of years |
| 18:17.59 | HcE | an embedded product uses perhaps 1 or 2 NAND flashes, a SSD uses 16 or more |
| 18:18.12 | ds2 | prpplague: IMO, if they choose to not use X, they are on their own as far as keyboard input is concerned ;) |
| 18:18.53 | MothaWork | HcE: yeah. What I'm hoping is that the smaller capacity devices will stick to the embedded market. Most embedded devices don't use >1GB of non-removable flash, and if they do, it's not a big deal to have a multi-chip solution which can guarantee a boot area anyway |
| 18:19.24 | ds2 | MothaWork: or they can use the solderable SD cards |
| 18:19.42 | prpplague | ds2: we can't have that attitude, we have to make it easy for the developer |
| 18:19.51 | MothaWork | ds2: similar to the multi-chip option, though some chips actually support SD boot |
| 18:20.50 | HcE | MothaWork: IIRC the bootrom supports boot from NAND, but not write |
| 18:21.14 | HcE | MothaWork: but you will need to double check that with the datasheet when that is available ;) |
| 18:21.31 | ds2 | prpplague: okay, why not provide a userspace event generator for the non X folks? |
| 18:21.51 | HcE | libboost? |
| 18:22.05 | ds2 | MothaWork: yes, but that can get tricky...i.e. on the OMAP it requires a very specific geometry/format |
| 18:22.19 | MothaWork | HcE: of course. I could probably get the datasheet if I needed to right now, but I have no application sadly |
| 18:22.23 | MothaWork | I've been wanting to play with AVR32 |
| 18:22.31 | prpplague | ds2: thats possible, just means 2x the work, since i'd have to do the work for x and then do the event generator |
| 18:22.54 | MothaWork | HcE: we use a fair bit of Atmel stuff, so our rep is pretty good about getting stuff for us |
| 18:23.02 | HcE | MothaWork: the good side that the bootrom is new, not copied from AT91 devices |
| 18:23.09 | ds2 | prpplague: yes, but that can be less hair pulling then doing it all in the kernel |
| 18:23.12 | MothaWork | HcE: GOOD! :) |
| 18:23.22 | MothaWork | does the SPI controller work correctly? :) |
| 18:23.30 | HcE | it looks good :) |
| 18:23.45 | ds2 | is Atmel going to stay as a company? |
| 18:23.49 | MothaWork | AT91 is neat and feature-rich, but quirky as hell |
| 18:24.03 | prpplague | ds2: its not that bad, as i prefer kernel space, it's easier for me |
| 18:24.07 | MothaWork | ds2: dunno. Microchip and ON want to buy them, but no word from Atmel other than "we're looking into it" on the offer |
| 18:24.08 | *** join/#edev bbradley (n=bbradley@78-105-167-16.zone3.bethere.co.uk) |
| 18:24.19 | MothaWork | I can't say I'd be happy to see the micros get sold off to Microchip |
| 18:25.28 | ds2 | prpplague: heh.. guess you are like me.... complain a lot but still prefer the kernel side sanity ;) |
| 18:25.51 | MothaWork | the kernel space APIs make sense |
| 18:25.59 | MothaWork | the user space ones are often confusing as hell |
| 18:26.05 | ds2 | MothaWork: I wish there was a resolution on that. Either of them is going to result in a lot of stuff going away I suspect |
| 18:26.20 | prpplague | yea, its not really a complaint per se, more i like to find better ways doing it since we will have this methodology again in the future |
| 18:26.31 | MothaWork | ds2: well, the buyout offer was joint. Microchip wanted some stuff and ON wanted different stuff. |
| 18:26.36 | ds2 | confusing? is that like saying niagra falls is a little trickle? :) |
| 18:27.00 | ds2 | MothaWork: I don't see how everything will survive in both companies regardless of how it is split |
| 18:27.04 | MothaWork | ds2: IIRC, Microchip wants the microcontrollers, ON wants the RF, and they want to sell off the ASIC stuff |
| 18:27.16 | MothaWork | ds2: well, AVR32 would likely disappear overnight or nearly so |
| 18:27.28 | ds2 | I think Atmel is the sole source of QFP packaged ARM's with MMUs |
| 18:27.39 | MothaWork | ds2: I think Microchip wants Atmel's ARM lineup to replace their flailing PIC32 line |
| 18:28.04 | MothaWork | ds2: sadly, I can't see them killing PIC in favor of AVR, nor can I see them keeping both alive, so such a sale would likely result in the eventual destruction of the 8-bit AVR line |
| 18:28.05 | HcE | anybody use the PIC32's? |
| 18:28.09 | prpplague | ds2: i've got about 90% of it working now |
| 18:28.14 | MothaWork | HcE: I've never heard of anybody using them, no |
| 18:28.34 | ds2 | MothaWork: unless they map it into a PIC2000xxxx series |
| 18:28.34 | HcE | the core is nice, MIPS, but peripheral selection seems poor |
| 18:28.50 | HcE | I would doubt Atmel would sell for 5 $ |
| 18:28.54 | HcE | + per share |
| 18:29.12 | prpplague | ds2: main problem at the momment is some of the keys have 4 chars available and some only have 3 |
| 18:29.24 | MothaWork | ds2: I don't see that happening, really. The entire allure of PIC for most users is long-term familiarity and lots of library code, none of which would really run on the AVR lineup |
| 18:29.33 | ds2 | MothaWork: but you haven't accounted for the other Atmel stuff -- touch sensors, USB stuff, their flash |
| 18:30.18 | MothaWork | ds2: One of the two wanted the flash/EEPROM. I don't remember which (Microchip would make sense as they make that stuff, but I think ON wanted it). Dunno about the touch sensors. USB would likely go with the microcontrollers. |
| 18:30.27 | ds2 | prpplague: And all of that is defineable from ioctls/sysfs/proc, right? :) |
| 18:30.55 | MothaWork | HcE: issue is that ON/Microchip have apparently hinted at their intent to go hostile |
| 18:31.11 | prpplague | ds2: no, why would it? |
| 18:31.26 | HcE | MothaWork: the deal is to complex IMO, three parties trying to buy Atmel and split it up... |
| 18:31.31 | MothaWork | though I don't think there's enough outstanding shares to do it... |
| 18:31.36 | ds2 | prpplague: possiblely for internationaliation? or ability to extend it? |
| 18:31.53 | HcE | MothaWork: nope, above 50 % is owned by goverment funds or something like that |
| 18:31.59 | prpplague | ds2: extend it in what way? |
| 18:32.04 | MothaWork | HcE: well, their current share price is at 3.88 (up 0.13 on the day), so the market doesn't seem to think the offer will go through |
| 18:32.09 | ds2 | Atmel has a lot of unique stuff |
| 18:32.19 | ds2 | prpplague: additional keysyms |
| 18:32.20 | MothaWork | it spiked back when the offer was made, but it has since dropped and not recovered |
| 18:32.31 | MothaWork | ds2: yes, they do. Lots of it is very good, too, if a little quirky |
| 18:32.40 | MothaWork | Their 802.15.4 radio has the best RF specs on the market, IIRC |
| 18:32.48 | prpplague | ds2: the driver just produces scancodes, so you can map it anyway you want |
| 18:33.39 | MothaWork | prpplague: the 2D matrix can account for different num of output codes on a key. Just have an entry that indicates array length (or null terminate it/pad it) |
| 18:33.49 | MothaWork | of course, it need not be a matrix, it could be a list of lists or something |
| 18:34.23 | prpplague | MothaWork: yea, all keys on the keyboard have 5 scancodes available |
| 18:34.52 | prpplague | MothaWork: just for the ones not used, i'm setting to null |
| 18:35.18 | MothaWork | prpplague: and then just ignore them and wrap back around to the beginning, I presume? |
| 18:35.27 | prpplague | yea |
| 18:35.37 | ds2 | prpplague: that won't work.... right now each key maps to N keysyms... someone might want a key to map to N+1 keysyms |
| 18:35.55 | prpplague | ds2: i don't follow you |
| 18:36.22 | MothaWork | ds2: just make the matrix bigger in that dimension and pad the rest with nulls. Wastes some space, but whatever |
| 18:36.45 | MothaWork | you're talking about a custom lookup table in that case, anyway |
| 18:36.58 | prpplague | ds2: ahh i get what you are saying |
| 18:37.03 | ds2 | prpplague: let's say '1' can do A, B, C right now.... but maybe someone in the future would like to do A, A w/2dots on top, B, C |
| 18:37.26 | ds2 | MothaWork: *nod* that works for a small keyboard |
| 18:37.42 | MothaWork | ds2: well, in this case, N is 4 (and 1 has a null entry), so you can add your extra thing anyway, but you can always increase N at the cost of memory usage |
| 18:37.45 | prpplague | ds2: yea, it isn't hardcoded, they could increase the matrix size if they wanted to, but i doubt anyone will |
| 18:37.50 | MothaWork | ds2: which this is |
| 18:38.10 | MothaWork | ds2, prpplague: a way around that would be an array of ptrs to null terminated arrays |
| 18:38.24 | MothaWork | or include a size in the first indirection |
| 18:38.33 | ds2 | and have that accessible via sysfs? |
| 18:38.41 | ds2 | runs away ;) |
| 18:38.50 | MothaWork | then the matrix need not have rows of identical size |
| 18:39.11 | MothaWork | ds2: I think if you're modifying the lookup table, you can be expected to just hit a .h file |
| 18:39.29 | prpplague | ds2: i hear what you are saying, but that is far beyond the capabilities of most of our customers |
| 18:40.28 | ds2 | prpplague: I was thinking ahead for when you push it upstream how it can be useful for other people... I had apps before that could have made use of that |
| 18:40.53 | prpplague | ds2: i hadn't made plans to push this upstream |
| 18:41.06 | ds2 | MothaWork: if it is purely for internationalization, that might not work; it might have to be dynamic |
| 18:41.22 | ds2 | prpplague: will it ever get pushed? |
| 18:41.39 | MothaWork | ds2: just have the user dump the whole table into sysfs at once, then, size fields and all |
| 18:41.46 | prpplague | ds2: doubt it |
| 18:41.57 | ds2 | prpplague: will it at least get posted somewhere? |
| 18:42.16 | ds2 | or are you going to do a strict interpretation of the GPL? |
| 18:42.23 | prpplague | yea i guess i could post it somewhere |
| 18:42.32 | prpplague | ds2: naw, everything is completely open |
| 18:43.16 | ds2 | prpplague: I have heard other people say that and by that they mean - if you bought their stuff, they will provide you and only you with the sources upon request and strongly encourage you to not distribute the source |
| 18:43.54 | prpplague | ds2: yea i am aware of that kind of compliance, however we are completely open with our source |
| 18:44.14 | ds2 | cool |
| 18:51.14 | prpplague | ds2: we've had some good stuff over the years, but just never got the time to prepare it and post it |
| 18:51.34 | prpplague | ds2: about 2 years ago, managment basically stopped allowing time for patch submissions |
| 18:53.39 | prpplague | CosmicPenguin: did you buy a bunch of stocks last week? |
| 18:59.41 | *** join/#edev steliosk (n=Stelios@79.107.27.111) |
| 19:02.05 | *** join/#edev prpplague (n=dave@mail.americanmicrosystems.com) |
| 19:14.48 | prpplague | ho ho hum |
| 19:24.19 | solar | yep |
| 19:31.04 | prpplague | ~seen landley |
| 19:31.08 | purl | landley <n=landley@static-71-162-243-5.phlapa.fios.verizon.net> was last seen on IRC in channel #elinux, 11d 22h 1m 36s ago, saying: 'And 4.2.2 has the exact same bug as 4.1.2.'. |
| 19:31.37 | prpplague | scanlime: you still working at VMWare? |
| 19:34.57 | scanlime | prpplague: yep |
| 19:35.31 | solar | has a few friends over there |
| 19:35.42 | prpplague | scanlime: a headhunter on linkedin was trolling for vmware the other day |
| 19:35.49 | scanlime | ugh |
| 19:42.12 | prpplague | solar: showed anyone at work the 8050? |
| 19:42.55 | solar | yep. chances are we will want to order 1-2 for each of our datacenters |
| 19:43.16 | prpplague | solar: cool! what will you use it for? |
| 19:43.50 | solar | Probably inventory control |
| 19:44.01 | solar | depends on what I can code up later on. |
| 19:44.14 | solar | the dataview gave me quite a few ideas |
| 19:44.23 | prpplague | ahh |
| 19:44.35 | prpplague | open source app? |
| 19:44.47 | solar | but need to be able to on the spot look up that barcode. If no matching entry exists then have our guys assign it on the spot |
| 19:45.29 | prpplague | solar: ahh easily doable |
| 19:59.28 | *** join/#edev g1powermac_PB (n=g1powerm@unaffiliated/g1powermac) |
| 20:00.56 | solar | prppr: we for sure need to find a battery applet |
| 20:23.05 | prpplague | solar: yea, i'm finishing the battery fuel gauge stuff now |
| 20:24.16 | adyer | solar: while [ 1 ]; do cat bat_stat; sleep 1; done :-) |
| 20:24.29 | *** join/#edev kergoth_ (n=kergoth@65.200.49.156) |
| 20:26.29 | solar | I think matchbox has some battery monitoring applet. |
| 20:26.52 | *** join/#edev magnetron (n=magnetro@unaffiliated/magnetron) |
| 20:27.30 | *** join/#edev Ian_Daniher (n=it@69.61.230.246) |
| 20:27.49 | kergoth_ | any of you guys used floating point in hex in C? i.e. 0x0.FFFFp+0? |
| 20:28.16 | MothaWork | that works? |
| 20:29.45 | kergoth_ | apparently. i just got a glibc bug report (customer requests a backport of a glibc upstream fix) about it |
| 20:30.02 | kergoth_ | printf("%.0LA", (long double) 0x0.FFFFp+0) is apparently supposed to output 0X1P+0 |
| 20:30.12 | kergoth_ | which makes my head hurt |
| 20:33.05 | MothaWork | mine as well.. |
| 20:33.20 | MothaWork | I didn't know you could use that notation, so the answer to your initial question is no :) |
| 20:33.48 | adyer | C99, just because you can do it, doesn't mean you should :-) |
| 20:35.18 | prpplague | solar: yea, the poky build i did had a battery monitor app |
| 20:35.28 | prpplague | solar: just didn't get to the point of setting it up |
| 20:38.14 | prpplague | solar: oh, and we need some sort of tray app that displays the status of numlock and capslock |
| 20:40.12 | MothaWork | adyer: that's a C99 feature? learn something every day, I guess. |
| 20:41.51 | adyer | MothaWork: looks like there are complex literals, too. |
| 20:50.43 | solar | prpplague: fan of dbus+hal being on the device? |
| 20:56.03 | prpplague | solar: not really, thats just what poky built |
| 20:57.08 | solar | prpplague: plz don't forget the following item today. wifi-driver/modules or whatever I'll need for network access. |
| 20:57.27 | solar | has been sitting here for the past ten mins fighting with the MMC/SD slot |
| 20:57.32 | prpplague | solar: you have the kernel source, you can build it if you want |
| 20:57.42 | prpplague | solar: no tweezers? |
| 20:57.54 | solar | not at work ;/ |
| 20:58.41 | solar | thinking for devel. It might be eaiser to just take all the plastic off |
| 21:01.04 | solar | ahh crap. I just jammed the MMC inbetwen where it's supposed to be |
| 21:01.19 | solar | dunno bro. Not sure that part of the design is 'great' |
| 21:07.33 | MothaWork | adyer: yes, but I knew about those |
| 21:07.45 | prpplague | solar: not my engineering on that |
| 21:08.12 | MothaWork | prpplague: how much you know about FCC certification of intentional radiators? |
| 21:08.27 | prpplague | MothaWork: sorry none |
| 21:08.41 | MothaWork | darn |
| 21:08.45 | prpplague | solar: yea if you want you can take the two pieces apart |
| 21:13.42 | kergoth | shoot, what did i do with that shell script that did a combinediff of more than two diffs |
| 21:13.50 | kergoth | think i used it a few jobs ago |
| 21:13.52 | kergoth | scratches head |
| 21:14.33 | solar | prpplague: We must of done something different. I just nuked the ext2 image. Put on mine. Rebooted and it went back to the poky image vs the one on the MMC. What did you do to get the error about fonts etc? |
| 21:15.51 | prpplague | solar: the default is to boot to the nand flash |
| 21:15.55 | solar | prpplague: also. I should probably not build modules. Unless I also rebuild/reflash the kernel. Your toolchain is not the exact same as the one I'm using. |
| 21:16.00 | prpplague | solar: you'll need to change the boot arguements in apex |
| 21:16.36 | solar | using the flyswatter? |
| 21:17.11 | prpplague | solar: from apex do: setenv cmdline "console=ttySAC1,115200 root=/dev/mmcblk0p1 rootdelay=3 fbcon=rotate:1" |
| 21:17.16 | prpplague | solar: from the serial console |
| 21:18.54 | solar | k will have to test that one from home. Did not bring that part of the device with me. |
| 21:19.01 | prpplague | ahh |
| 21:19.25 | prpplague | i exclusively use the serial console for all my dev |
| 21:25.02 | prpplague | man someone made alot of money today |
| 21:26.59 | prpplague | anyone got a guess on what processor is in the G1 phone? |
| 21:31.33 | MothaWork | prpplague: as a straight up guess out of the blue, I'd say S3Cxxxx or an OMAP |
| 21:31.53 | prpplague | MothaWork: yea, i was thinking a 6410 |
| 21:31.56 | prpplague | s3c6410 |
| 21:31.57 | MothaWork | of course, that covers like 85% of the smartphone market, so... |
| 21:32.10 | *** join/#edev EI5GTB__ (n=Paul@78.16.131.207) |
| 21:37.16 | prpplague | hmm |
| 21:44.51 | prpplague | GPSFan: ping |
| 21:44.58 | GPSFan | prpplague: pong |
| 21:45.53 | prpplague | GPSFan: re zipitv2 wifi - http://lists.infradead.org/pipermail/libertas-dev/2008-October/002007.html |
| 21:46.07 | GPSFan | looks |
| 21:48.26 | GPSFan | prpplague: my goodness, looks like real progress..;>) |
| 21:48.32 | prpplague | indeed |
| 21:49.27 | solar | prpplague: 6410 or 2410? |
| 21:49.37 | prpplague | 6410 |
| 21:49.50 | prpplague | arm11 |
| 21:49.52 | GPSFan | prpplague: might be time to poke at the z2 kernel again, and see how bad it is to update to 2.6.27 or so... |
| 21:50.04 | solar | no linux-kernel support for that yet is there? |
| 21:50.49 | prpplague | solar: nothing that is main tree, but it ships with a linux bsp |
| 21:50.58 | prpplague | from montavista iirc |
| 21:51.26 | ds2 | Hmmm 6410 samsung? Hmmm |
| 21:53.06 | prpplague | solar: supposedly the iPhone is 6400 based |
| 22:00.23 | GPSFan | prpplague: btw thanks... |
| 22:00.38 | prpplague | np, just wish i had more time to work on it |
| 22:20.35 | *** part/#edev adyer (n=adyer@adsl-69-223-13-78.dsl.chcgil.ameritech.net) |
| 22:24.01 | *** join/#edev methril|laptop (n=methril@23.73.220.87.dynamic.jazztel.es) |
| 22:26.49 | *** join/#edev CosmicPenguin (n=nobody@163.181.251.103) |
| 22:26.49 | *** mode/#edev [+o CosmicPenguin] by ChanServ |
| 22:28.32 | solar | Any Deb guru's around that have worked with preseed.cfg much? |
| 22:36.35 | ds2 | so square roots work |
| 23:19.04 | *** join/#edev Ian_Daniher (n=it@69.61.230.246) |
| 23:20.42 | ds2 | anyone know if anything special is needed to use NPTL? i.e. does the same -lpthreads work and the library takes care of the magic? |
| 23:22.55 | agaffney | I thought it was binary compatible in most cases |
| 23:54.53 | *** join/#edev g1powermac_PB (n=g1powerm@unaffiliated/g1powermac) |
| 23:59.48 | solar | agaffney: http://tinyurl.com/walmart-femine-hygiene-spray (whats wrong with this?) |