| 01:16.31 | *** join/#edev AtomicToad (i=JohnnyL@ool-182ddad4.dyn.optonline.net) |
| 01:16.48 | *** part/#edev AtomicToad (i=JohnnyL@ool-182ddad4.dyn.optonline.net) |
| 01:44.58 | *** join/#edev kergoth (n=kergoth@ip72-201-11-30.ph.ph.cox.net) |
| 01:47.10 | *** join/#edev kergoth_ (n=kergoth@ip72-201-11-30.ph.ph.cox.net) |
| 02:02.14 | *** join/#edev kergoth_ (n=kergoth@ip72-201-11-30.ph.ph.cox.net) |
| 02:58.16 | *** join/#edev landley (n=landley@cpe-70-116-30-223.austin.res.rr.com) |
| 02:58.16 | *** mode/#edev [+o landley] by ChanServ |
| 03:12.57 | *** join/#edev mbuf (n=user@61.16.248.242) |
| 04:19.42 | *** join/#edev redblue (i=star@ppp058.108-253-207.mtl.mt.videotron.ca) |
| 04:37.57 | *** join/#edev DrZimmerman (n=theo@77-56-228-246.dclient.hispeed.ch) |
| 04:40.10 | *** part/#edev JohnnyL (i=JohnnyL@ool-182ddad4.dyn.optonline.net) |
| 04:43.54 | *** join/#edev kergoth (n=kergoth@ip72-201-11-30.ph.ph.cox.net) |
| 05:13.50 | *** join/#edev harpal (n=Harpal@122.169.108.195) |
| 05:29.32 | *** join/#edev g1powermac_PB (n=g1powerm@unaffiliated/g1powermac) |
| 05:59.51 | *** join/#edev linac (n=lin@125.77.74.181) |
| 07:14.11 | *** join/#edev JoeLlama (n=snork@unaffiliated/joellama) |
| 07:15.27 | *** join/#edev roxfan (n=dunno@134.63-244-81.adsl-dyn.isp.belgacom.be) |
| 07:34.23 | *** join/#edev nuix (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 07:35.59 | *** part/#edev nuix (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 07:40.12 | *** join/#edev lyakh (n=lyakh@p57BD2A4C.dip0.t-ipconnect.de) |
| 07:51.57 | *** join/#edev nuix (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 07:52.06 | *** part/#edev nuix (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 07:52.16 | *** join/#edev nuix (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 08:05.47 | *** join/#edev steliosk (n=Stelios@ipa107.2.tellas.gr) |
| 08:08.03 | methril | yo |
| 08:14.37 | *** join/#edev nuix2 (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 08:18.46 | *** join/#edev [AD]Turbo (n=turbo@host102-246-dynamic.7-87-r.retail.telecomitalia.it) |
| 08:21.04 | [AD]Turbo | yo |
| 08:44.34 | *** join/#edev nuix (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 08:50.18 | *** join/#edev roxfan2 (n=dunno@49.43-244-81.adsl-dyn.isp.belgacom.be) |
| 09:00.43 | *** join/#edev hw (n=hw@p578b3905.dip0.t-ipconnect.de) |
| 10:00.05 | *** join/#edev steliosk (n=Stelios@ipa107.2.tellas.gr) |
| 10:00.48 | *** join/#edev g1powermac (n=g1powerm@unaffiliated/g1powermac) |
| 12:48.46 | *** join/#edev mbuf` (n=user@61.16.248.242) |
| 12:50.59 | *** join/#edev BitSlop__ (n=BitSlop@mail.forwardengineering.com) |
| 13:20.11 | *** join/#edev dijenerate (n=dijenera@72.22.149.228) |
| 13:33.28 | *** join/#edev Chocobo (n=swinchen@strongbad.eece.maine.edu) |
| 13:35.44 | Chocobo | Anyone here use pcb.sf.net? I can not for the life of me figure out the "Realign Grid" feature. I think it might just be broken. |
| 13:37.40 | *** join/#edev Crofton (n=balister@12.234.232.66) |
| 13:40.41 | *** join/#edev mbuf` (n=user@61.16.248.242) |
| 13:40.41 | *** join/#edev lyakh (n=lyakh@p57BD2A4C.dip0.t-ipconnect.de) [NETSPLIT VICTIM] |
| 13:40.41 | *** join/#edev beewoolie (n=beewooli@66.147.194.238) [NETSPLIT VICTIM] |
| 13:40.41 | *** join/#edev mpk (n=mpk@aggr.com) |
| 13:40.41 | *** join/#edev morrijr (n=john@cpc2-mfld9-0-0-cust297.nott.cable.ntl.com) [NETSPLIT VICTIM] |
| 13:40.42 | *** join/#edev dmead (n=dan@ip226.sensaphone.us) [NETSPLIT VICTIM] |
| 13:40.42 | *** join/#edev ohsix (i=ohsix@66.220.111.222) [NETSPLIT VICTIM] |
| 13:40.42 | *** join/#edev dfarnsworth (n=dfarnswo@65.200.49.156) [NETSPLIT VICTIM] |
| 14:05.51 | *** join/#edev GPSFan (n=kenm@64.92.145.112) |
| 14:05.51 | *** mode/#edev [+o GPSFan] by ChanServ |
| 14:09.30 | *** join/#edev kergoth (n=kergoth@ip72-201-11-30.ph.ph.cox.net) |
| 14:12.28 | *** join/#edev mbuf (n=user@61.16.248.242) |
| 14:18.09 | *** join/#edev prpplague (n=dave@mail.americanmicrosystems.com) |
| 14:29.33 | *** join/#edev lifeeth (n=Praneeth@unaffiliated/lifeeth) |
| 14:37.03 | *** join/#edev samrobb (n=samrobb@eng.arriad.com) |
| 14:39.04 | *** join/#edev ramas_rtl (n=latini@83-103-42-2.ip.fastwebnet.it) |
| 14:53.11 | *** join/#edev kergoth (n=kergoth@65.200.49.156) |
| 14:55.10 | *** join/#edev kergoth (n=kergoth@65.200.49.156) |
| 14:55.35 | kergoth | morning |
| 14:58.06 | *** join/#edev linac (n=lin@121.201.61.181) |
| 15:15.22 | *** join/#edev gandhijee (n=root@host-66-202-34-165.spr.choiceone.net) |
| 15:17.46 | *** join/#edev linac (n=lin@121.201.39.103) |
| 15:32.44 | *** join/#edev jerm^ (n=chatzill@216.68.89.80) |
| 15:37.02 | *** join/#edev sunrunner20 (n=jamesdoe@pool-71-164-205-30.dllstx.fios.verizon.net) |
| 15:39.11 | *** join/#edev BitSlop_ (n=BitSlop@mail.forwardengineering.com) |
| 15:39.35 | *** join/#edev beewoolie (n=beewooli@66.147.194.238) |
| 15:39.52 | sunrunner20 | yall konw of a way to control spi over usb? |
| 15:41.02 | prpplague | sunrunner20: need to be a little more specific as to what you want to accomplish |
| 15:43.41 | *** join/#edev beewoolie (n=beewooli@66.147.194.238) |
| 15:44.13 | prpplague | sunrunner20: if you simpy want a usb->spi device, the ft2232 is more than capable |
| 15:44.15 | sunrunner20 | http://datasheets.maxim-ic.com/en/ds/MAX6675.pdf interface w/ that via usb |
| 15:44.38 | prpplague | looks |
| 15:45.11 | prpplague | sunrunner20: ft2232 is the easiest choice |
| 15:46.37 | prpplague | sunrunner20: http://www.dlpdesign.com/usb/2232m.shtml |
| 15:49.12 | MothaWork | I actually built a USB to SPI interface pod when I worked at ON |
| 15:49.32 | MothaWork | it has a bunch of other "hidden" features, too, though |
| 15:49.37 | prpplague | hehe |
| 15:49.44 | MothaWork | actually uses an AVR |
| 15:49.54 | MothaWork | a rather big one, in fact |
| 15:50.27 | *** join/#edev Madsy (n=madsy@ti500710a342-2586.bb.online.no) |
| 15:50.27 | prpplague | yea, i like the ft2232 modules since they have spi, i2c, gpio, uarts, and jtag |
| 15:50.36 | prpplague | multi-use device |
| 15:51.07 | sunrunner20 | yay |
| 15:51.51 | sunrunner20 | thx, thats what i needed |
| 15:51.58 | *** join/#edev CosmicPenguin (n=nobody@163.181.251.103) |
| 15:51.58 | *** mode/#edev [+o CosmicPenguin] by ChanServ |
| 15:52.13 | sunrunner20 | time to order/sample |
| 15:52.45 | sunrunner20 | know where to get cheap type type ks? |
| 15:52.49 | prpplague | sunrunner20: the ft2232 makes it very easy to evaluate devices that use i2c or spi from your desktop pc |
| 15:52.56 | prpplague | sunrunner20: ?? |
| 15:53.15 | sunrunner20 | type k thermocouple |
| 15:53.52 | prpplague | sorry no |
| 15:55.28 | *** join/#edev samrobb_ (n=samrobb@eng.arriad.com) |
| 15:59.19 | *** part/#edev ramas_rtl (n=latini@83-103-42-2.ip.fastwebnet.it) |
| 16:08.38 | Chocobo | When hooking up jtag to a micro... should the RST pin be connected to anything? I am confused by trst and rst. |
| 16:09.07 | prpplague | ChanServ: nTRST is the line to reset the JTAG interface, nRST is the line to reset the processor |
| 16:09.49 | prpplague | Chocobo: generally what occures is the jtag debugging device will generate a nTRST to reset the jtag, then generate a reset on the processor |
| 16:10.11 | prpplague | Chocobo: however not all device support this operation, so many times the nRST and nTRST are tied together |
| 16:11.09 | Chocobo | prpplague, ok.. so my processor does not have an nTRST line... but it does have a nRST (where I assume the lowercase n means active low) this is the JTAG interface I am using http://www.olimex.com/dev/images/arm-jtag-layout.gif I should connect RST up to RST on my processor? |
| 16:11.29 | Chocobo | by device do you mean processor or jtag pod? |
| 16:11.41 | prpplague | Chocobo: your processor should have a nTRST line |
| 16:11.54 | prpplague | Chocobo: processor |
| 16:12.52 | Chocobo | Nope.. I have looked for it over and over... |
| 16:14.12 | MothaWork | prpplague: many do lack it |
| 16:14.53 | prpplague | MothaWork: didn't know that, interesting |
| 16:16.21 | Chocobo | Yeah, so I am not sure if I should hook the jtag nTRST line up to the nRST line on the processor, or if I should hook the nRST (jtag) to the nRST line (processor). I am probing voltages and the nRST line coming out of the JTAG connector is 0 volts... it should be 3.3v |
| 16:18.15 | Chocobo | And I am not even really sure where to ask my question. |
| 16:18.24 | *** join/#edev chouimat|work (n=dieu@209.217.106.98) |
| 16:18.33 | beewoolie | Chocobo: I don't think that's a good idea. |
| 16:18.54 | Chocobo | beewoolie, which one? |
| 16:19.07 | beewoolie | The nTRST line is a TAP reset. It's optional. |
| 16:19.07 | MothaWork | prpplague: some just rely on the fact that you can run like 50 TCK clocks with TMS held in a certain state to always reset the JTAG state machine |
| 16:19.19 | prpplague | MothaWork: ahh |
| 16:19.38 | beewoolie | MothaWork: You only need to cycle eight times. |
| 16:19.40 | MothaWork | and, worst case, just reset the whole darned board, and you'll know what state everything is in :) |
| 16:19.49 | MothaWork | beewoolie: I thought 50 sounded high :) |
| 16:19.50 | prpplague | Chocobo: yea, just use nRST to your processor reset signal |
| 16:20.06 | beewoolie | Chocobo: right. |
| 16:21.35 | Chocobo | I don't know (with openocd) how to toggle the nRST line. I am watching it with an o-scope. hrmm |
| 16:22.09 | Chocobo | The 8 cycles... is that considered a srst? |
| 16:22.11 | prpplague | Chocobo: there is a specific command to do that in openocd once you are up and running |
| 16:22.20 | Chocobo | I am up an running |
| 16:22.20 | prpplague | Chocobo: but it is normally handled by openocd |
| 16:22.52 | Chocobo | the 0 volt RST line is worrisome to me. |
| 16:22.54 | MothaWork | 8 TCK cycles with TMS held in a certain state (I think low) will reset the JTAG state machine inside the device. SRST is the system reset net |
| 16:23.14 | MothaWork | where are you measuring 0V? |
| 16:23.16 | Chocobo | lol. Where do I learn this stuff? JTAG is like a total mystery to me. |
| 16:23.58 | Chocobo | MothaWork, I am measuring it on the RST line on the JTAG connector (not currently connected to the microcontroller. (maybe it just needs a pull-up?) |
| 16:24.16 | MothaWork | target device side or JTAG pod side? |
| 16:24.40 | MothaWork | on most systems, RST is an open drain/open collector net and needs a pull-up, yes, but that should be on the board already |
| 16:25.09 | MothaWork | if you're measuring 0V on the JTAG pod connector when it is not connected to anything, it will probably output 0 since it has no VTref |
| 16:25.14 | Chocobo | jtag pod side. I currently have no connection from JTAG <---> processor (nRST line only) |
| 16:25.40 | MothaWork | that said, RST output from the pod is likely open drain |
| 16:26.03 | Chocobo | Ok, I will try I weak pull-up and see how that does. |
| 16:26.22 | MothaWork | just plug it in to the target device |
| 16:26.26 | MothaWork | that will provide VTref, too |
| 16:28.18 | prpplague | Chocobo: JTAG is one of those things you have to work at, information is hard to gather |
| 16:29.10 | prpplague | Chocobo: the nRST line is normally used with a pullup, so if you are checking the nRST on the pod side while it is unconnected to the processor's reset, you will probably measure 0V because it is not being pulled up |
| 16:29.37 | *** join/#edev davidc__ (n=davidc__@S01060002b360aacd.vc.shawcable.net) |
| 16:29.46 | Chocobo | I have Vref, and Vtarget tied to 3.3v (from the board), TCK, TMS, TDI and TDO. I am just not doing anythign with the RST line right now. |
| 16:29.48 | prpplague | davidc__: hey hey bud!! |
| 16:30.09 | prpplague | Chocobo: right, which means you probably will see the voltage at 0v |
| 16:30.55 | davidc__ | hey prpplague. How goes it? |
| 16:31.07 | Chocobo | Yeah, I will try a 10K pullup or something and see if that works. I hope I have some free pins to connect to :P |
| 16:31.26 | prpplague | davidc__: it goes, and you? |
| 16:31.53 | davidc__ | prpplague: pretty good; nothing much happening here |
| 16:43.06 | sunrunner20 | wow |
| 16:43.15 | sunrunner20 | the FT2232D is pricy |
| 16:43.33 | prpplague | sunrunner20: only as a module |
| 16:43.40 | sunrunner20 | $7 for the chip |
| 16:43.44 | prpplague | sunrunner20: it normally runs about $4 in small qty |
| 16:43.51 | prpplague | sunrunner20: where from? |
| 16:43.56 | sunrunner20 | mouser/digi |
| 16:44.15 | prpplague | sunrunner20: you only buying a couple? |
| 16:44.19 | sunrunner20 | one |
| 16:44.36 | prpplague | sunrunner20: better to purchase the module and save some time and money |
| 16:45.27 | sunrunner20 | sparkfun? |
| 16:46.09 | prpplague | sunrunner20: mouser/digikey |
| 16:46.12 | prpplague | sunrunner20: i gave you the url |
| 16:46.47 | prpplague | sunrunner20: http://www.dlpdesign.com/usb/2232m.shtml |
| 16:50.55 | prpplague | CosmicPenguin: ping |
| 16:52.17 | sunrunner20 | might need to because of the pitch |
| 16:52.42 | CosmicPenguin | prpplague: pong |
| 16:53.16 | prpplague | CosmicPenguin: input subsystem mailing list? any idea ? |
| 17:05.20 | CosmicPenguin | no |
| 17:05.21 | CosmicPenguin | sorry |
| 17:05.52 | kergoth | prpplague: http://vger.kernel.org/vger-lists.html#linux-input |
| 17:06.01 | sunrunner20 | wait, so I can have my SPI on channel A and put a serial adapter on channel B? |
| 17:06.05 | prpplague | kergoth: ahh thanks |
| 17:06.13 | prpplague | sunrunner20: yea |
| 17:06.15 | kergoth | np |
| 17:06.21 | sunrunner20 | ^_^ |
| 17:06.27 | kergoth | 's been resubscribing to a lot of mailing lists lately |
| 17:08.04 | sunrunner20 | man this sucks that they only offer it w/ .5mm pitch |
| 17:08.32 | prpplague | kergoth: see how badly i get flamed for this patch |
| 17:08.38 | kergoth | heh |
| 17:08.39 | kergoth | what patch? |
| 17:09.11 | prpplague | a combination patch to add generic led event handler to the input system, and generic led event triggers to the leds systems |
| 17:10.12 | kergoth | ah |
| 17:10.24 | kergoth | what's it for? |
| 17:10.26 | prpplague | kergoth: wanna have a look before i post it? |
| 17:10.53 | kergoth | sure, doubt i'll be helpful, I'm wayyy too rusty, but it may help me brush up on things :) |
| 17:19.46 | prpplague | kergoth: http://pastebin.ca/1245991 |
| 17:21.03 | kergoth | prpplague: looks like INPUT_GENERICLEDS has a copy/pasted description of something else |
| 17:21.12 | kergoth | in the Kconfig |
| 17:21.41 | *** join/#edev nuix2 (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 17:21.48 | prpplague | kergoth: oops indeed |
| 17:22.03 | kergoth | don't see anything else offhand, too rusty with input :) |
| 17:22.19 | MothaWork | prpplague: apparently you don't have the same view on LEDs that the MTD people do |
| 17:22.28 | prpplague | MonMotha: ?? |
| 17:22.54 | MothaWork | the MTD driver has a comment to the effect of "...for systems that report every fart in the system on a unique LED. This gets optimized out if LED support is off." |
| 17:23.23 | MothaWork | MTD NAND driver, I should say |
| 17:26.40 | prpplague | MonMotha: well i can understand their attitude with regards to MTD, but we have to have a number of leds that correspond to things such as numlock and capslock as well as led events related to input such as good/bad barcode scans |
| 17:26.55 | prpplague | MonMotha: it is a pain in the ass to hardcode these leds everytime |
| 17:27.41 | *** join/#edev Geicus (n=chatzill@64.132.1.226) |
| 17:28.24 | MothaWork | prpplague: that's quite a lot more legitimate |
| 17:28.40 | prpplague | kergoth: yea, when i was moving the code forward to 2.6.27, i did a cut-n-paste typo |
| 17:28.46 | kergoth | ah |
| 17:33.19 | *** join/#edev nuix (n=alex@209.112.246.162) |
| 17:33.34 | prpplague | nuix: greetings |
| 17:34.01 | nuix | Hello! |
| 17:38.26 | nuix | prppplague: I am thinkung about getting a Hammer. It seems to have evrything I need, but I also need to do some work on a NAND flash. Can you recommend any NAND flash for Hammer kit? |
| 17:38.28 | *** join/#edev EI5GTB__ (n=Paul@213-202-187-243.bas504.dsl.esat.net) |
| 17:42.37 | prpplague | nuix: the nand flash controller for the s3c2410 is not brought out to pins on the hammer, however you can bitbang a nand interface very easily with 8 gpio for address/data, and 4 gpio for controls |
| 17:42.48 | prpplague | nuix: my suggestion is to use an xD card |
| 17:43.20 | prpplague | nuix: you can get an inexpensive xD card reader(about $5USD) and remove the socket for use with the hammer |
| 17:44.24 | nuix | prpplague: Great tip! Many thanks. I am going to try that. |
| 17:54.56 | prpplague | the hagis is in the fire now |
| 17:56.57 | kergoth | hmm |
| 17:58.43 | prpplague | kergoth: are you on the linux-input list? |
| 17:58.51 | kergoth | don't think so, not yet anyway |
| 17:59.16 | prpplague | ahh ok |
| 17:59.41 | prpplague | doesn't look as though there is an active archive online |
| 18:00.39 | kergoth | prpplague: http://news.gmane.org/gmane.linux.kernel.input |
| 18:01.20 | prpplague | ahh dandy |
| 18:02.33 | prpplague | kergoth: i suspect that since i'm new to the list my post will need moderator approval |
| 18:14.10 | *** join/#edev lyakh (n=lyakh@p57BD2A4C.dip0.t-ipconnect.de) |
| 18:16.37 | prpplague | doesn't feel good today |
| 18:24.46 | *** join/#edev Ian_Daniher (n=it@204.10.219.119) |
| 18:34.15 | prpplague | kergoth: well no flames yet |
| 18:34.37 | prpplague | kergoth: what is the old saying "no news is good news" |
| 18:34.44 | *** join/#edev DrZimmerman (n=theo@77-56-228-246.dclient.hispeed.ch) |
| 18:42.38 | prpplague | i just don't get, why are there so many job postings with visual c/c++ and linux experience |
| 18:43.17 | prpplague | those two just don't seem right together |
| 18:45.10 | MothaWork | prpplague: likely HR misunderstanding requirements |
| 18:49.59 | CosmicPenguin | prpplague: ping |
| 18:53.37 | prpplague | CosmicPenguin: pong |
| 18:54.09 | prpplague | MothaWork: yea, i can understand 1 or 2 postings, but i count 20+ current postings with those combinations |
| 19:00.33 | beewoolie | prpplague: those would be liars. |
| 19:02.29 | prpplague | beewoolie: job hunting is going to be a common pastime soon |
| 19:09.16 | beewoolie | prpplague: So the event stream would see notification of setting an LED. Interesting. |
| 19:11.09 | prpplague | beewoolie: yea, the leds class allows you easily define leds from your machine file, however associating them with specific events normally had to occure in userland |
| 19:11.56 | prpplague | beewoolie: this allows you to match leds from the leds class with events in the input system, such as capslock and numlock |
| 19:15.09 | *** join/#edev roxfan (n=dunno@49.43-244-81.adsl-dyn.isp.belgacom.be) |
| 19:19.00 | beewoolie | prpplague: I'm not sure I quite get it. I think of LEDs as annunciators. The real event is pressing the CapsLock key. Something responds to the event and sets the LED. How does your patch change this? |
| 19:21.14 | *** join/#edev kergoth (n=kergoth@65.200.49.156) |
| 19:22.37 | prpplague | beewoolie: one sec |
| 19:24.57 | prpplague | beewoolie: not all devices have a "capslock" key |
| 19:25.28 | prpplague | beewoolie: and the led to display the capslock status might not be part of the keypad itself |
| 19:25.46 | prpplague | beewoolie: for instances, the capslock and number leds are just on gpios |
| 19:26.15 | prpplague | beewoolie: if you do a keypad driver that turns these on/off, you are hardcoding the information for the gpio directly into the keypad driver |
| 19:26.48 | prpplague | beewoolie: with this method, keeping with the class driver structures, all of the actual mapping is done in the machine definition file |
| 19:27.00 | prpplague | beewoolie: no hardware specific information is actually in the driver |
| 19:28.43 | *** join/#edev samrobb (n=samrobb@eng.arriad.com) |
| 19:29.32 | samrobb | iac, tell me about sam |
| 19:29.40 | samrobb | IAC |
| 19:29.50 | samrobb | Whoops, wrong window :-) |
| 19:29.51 | prpplague | beewoolie: if you look at a linux kernel source, a good example of this is the wistron laptop driver linux-2.6.27/drivers/input/misc/wistron_btns.c |
| 19:30.09 | beewoolie | prpplague: No issue with that. The part I don't quite see is why is this an LED event? Is it something like the key driver can send the event and let a handler do the right thing? So it sends a "CAPSLOCK_LED" event. |
| 19:31.43 | prpplague | beewoolie: yea, if you look at the include/linux/input.h , you will see there are a number of led events defined, such as EV_CAPSLOCK and EV_NUMLOCK |
| 19:31.58 | prpplague | beewoolie: when you press the capslock button , two events are generated |
| 19:32.04 | prpplague | beewoolie: a key event and a led event |
| 19:32.28 | prpplague | beewoolie: normally the led event is hardcoded into the driver and never leaves the keyboard driver |
| 19:32.42 | beewoolie | prpplague: check. Nice addition. |
| 19:33.16 | prpplague | wonders is saying that just to make prpplague shutup, hehe |
| 19:56.13 | prpplague | beewoolie: if you run evtest on your desktop and press the caps lock key, you can see the reported events |
| 20:04.13 | CosmicPenguin | cosmic.amd.com signing off - its been fun |
| 20:13.52 | prpplague | in case anyone is wondering, cosmic just got laid-off |
| 20:14.13 | prpplague | along with 499 other people |
| 20:20.20 | roxfan | ouch |
| 20:21.02 | kergoth | ugh, that sucks :( |
| 20:21.04 | wmat | shitty |
| 20:22.41 | keesj | sucks indeed |
| 20:23.01 | prpplague | they gave him 10 minutes to pack up and leave |
| 20:23.27 | file | yikes |
| 20:25.41 | keesj | is this in US ok UK? |
| 20:26.56 | prpplague | keesj: the US |
| 20:28.47 | keesj | bugger |
| 20:28.51 | wmat | 10 minutes! that's cold. |
| 20:32.57 | kergoth | prpplague: ... that's terrible |
| 20:36.20 | prpplague | specially due to cosmics long service with amd |
| 20:36.43 | prpplague | i think he was headed to a brew pub |
| 20:37.06 | *** join/#edev L_Deluxe (n=lou@c-68-53-134-58.hsd1.tn.comcast.net) |
| 20:37.16 | kergoth | no doubt |
| 20:41.29 | *** join/#edev kantor (i=bird@79.114.19.183) |
| 20:42.48 | kantor | hi, is there an open source OSEK (Open Systems and their Interfaces for the Electronics in Motor Vehicles) operating system emulator ? |
| 20:43.50 | prpplague | kantor: kind of a vague question, there are a number of emulation systems that run under linux, including emulator for various arm, x86, ppc, and mips devices |
| 20:46.42 | *** join/#edev Geicus (n=chatzill@64.132.1.226) |
| 20:46.43 | prpplague | http://www.csai.tsinghua.edu.cn/est/Eng/materials/OSEKLinux.pdf?pt=1 |
| 20:47.11 | kantor | thanks |
| 20:47.49 | prpplague | kantor: from an initial look, i don't see any reason you couldn't run some OSEK based OS on any of the qemu stuff |
| 20:48.37 | prpplague | http://www.linuxworld.com/events/2008/EL3-080804_02:44:46.ppt |
| 20:52.03 | keesj | 91.171.235.23 maemo.mmapps.net - [05/Nov/2008:21:35:58 +0100] "GET /kees_groote_pimel.html HTTP/1.1" 200 80 "-" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506)" |
| 20:52.54 | keesj | sorry |
| 20:53.03 | keesj | pimel = dick.. |
| 20:53.10 | prpplague | ~lart keesj |
| 20:53.10 | purl | throws a AN/M-8 smoke grenade at keesj |
| 20:54.24 | keesj | wonders when google start picking that up. |
| 20:55.32 | keesj | is lookin forward to CELF Embedded Linux Conference Europe |
| 21:16.31 | mnemoc | where will it be? |
| 21:21.00 | *** join/#edev DrZimmerman (n=theo@77-56-228-246.dclient.hispeed.ch) |
| 21:21.31 | mnemoc | found, Ede :( |
| 21:30.21 | mnemoc | oh, it starts tomorrow |
| 21:32.49 | keesj | yes ede |
| 21:33.19 | keesj | http://www.embeddedlinuxconference.com/elc_europe08/ |
| 21:34.26 | *** join/#edev Geicus (n=chatzill@64.132.1.226) |
| 21:47.35 | *** join/#edev JoeLlama (n=snork@unaffiliated/joellama) |
| 21:55.10 | *** join/#edev g1powermac_PB (n=g1powerm@unaffiliated/g1powermac) |
| 21:56.40 | g1powermac_PB | well, I'm home and alive |
| 21:56.48 | g1powermac_PB | surgery was done this morning |
| 21:57.01 | solar | glad to hear it. |
| 21:57.19 | solar | I know that was stressing you out some.. the wait+wait+more-wait |
| 21:57.25 | g1powermac_PB | yup |
| 21:57.49 | g1powermac_PB | btw, general anaestesia sucks |
| 21:58.16 | prpplague | g1powermac_PB: good deal |
| 21:58.30 | g1powermac_PB | and they don't give pain meds till after you wake up |
| 21:58.47 | g1powermac_PB | man, those first ten minutes was horrid |
| 22:00.24 | g1powermac_PB | besides that, I'm not in much pain, and I haven't had any pain meds since after waking up |
| 22:00.38 | g1powermac_PB | which was about 9am ish |
| 22:04.17 | g1powermac_PB | anyway, good news is that there were no complications during the surgery with my heart rate |
| 22:08.29 | *** join/#edev nuix2 (n=store@cpe-76-93-178-138.san.res.rr.com) |
| 22:24.54 | *** join/#edev CP|home (n=nobody@www.crouse-house.com) |
| 22:25.41 | prpplague | CP|home: pick up some brew on the way home? |
| 22:26.55 | CP|home | well, here we are |
| 22:28.51 | prpplague | indeed |
| 22:44.43 | ds2 | what happened to cosmic.amd.com? |
| 22:46.07 | CP|home | it has been downsized |
| 22:46.07 | prpplague | ds2: cosmic has departed from amd |
| 22:48.38 | ds2 | ah :( |
| 22:51.49 | prpplague | ho ho hum |
| 22:58.16 | CP|home | gah - thunderbird sucks |
| 22:58.21 | CP|home | I need to mutt up at home |
| 22:58.26 | CP|home | plenty of time to do it.... |
| 23:01.30 | kergoth | CP|home: sorry to hear about the job, that sucks man :( |
| 23:01.56 | CP|home | thanks - these things happen, I guess |
| 23:02.02 | prpplague | CP|home: shall i packup one of the M8050 to ya? hehe |
| 23:02.15 | CP|home | We have all been there... |
| 23:02.33 | kergoth | aye |
| 23:04.11 | CP|home | prpplague: not sure what sort of value I can add... |
| 23:04.48 | prpplague | CP|home: no telling, i just want people hacking on it |
| 23:06.44 | roxfan | M8050? |
| 23:08.46 | CP|home | prpplague: i guess, if you want - but I can't promise you much |
| 23:08.59 | CP|home | its been a long time since I've hacked in that world |
| 23:09.03 | prpplague | roxfan: http://www.elinux.org/M8050 |
| 23:09.30 | roxfan | ah, your handheld |
| 23:09.34 | prpplague | CP|home: maybe time to get your ARM skills sharped |
| 23:09.48 | roxfan | it's got wince on it? :) |
| 23:10.55 | prpplague | roxfan: hehe, not yet atleast |
| 23:11.06 | prpplague | roxfan: just a screen shot the ME used to do a rendering |
| 23:11.16 | roxfan | i see |
| 23:11.48 | ds2 | prpplague: will the M8050 be waterproof? |
| 23:12.24 | prpplague | ds2: IP-65 rated, so it is "water resistant" but can't be submerged |
| 23:13.02 | ds2 | I see |
| 23:13.19 | ds2 | does IP-65 allow running over it with a 18 wheeler? |
| 23:13.46 | CP|home | only a 9 wheeler |
| 23:14.32 | prpplague | ds2: iirc 4' drop to concrete |
| 23:14.53 | ds2 | so this is less rugged then those toughbooks |
| 23:15.55 | prpplague | the 8050 is less rugged, but the 8000 will be pretty tough |
| 23:16.12 | prpplague | ds2: the 8050 was designed to be used in retail environments |
| 23:16.20 | prpplague | ds2: i.e. for line busting |
| 23:16.44 | ds2 | Hmm I see |
| 23:17.03 | ds2 | a fully ruggedized handheld would be nice |
| 23:17.48 | prpplague | ds2: like i said, it is IP-65, ruggedized is somewhat a vague description, in the same way as "embedded" is somewhat vague |
| 23:18.55 | ds2 | prpplague: *nod* I was thinking more of something can be submerged to at least 10M and can be run over... I guess something like a hand held in one of those pelican cases but still useable while inside it |
| 23:19.32 | prpplague | ds2: what kind of environment did you have in mind? |
| 23:19.58 | ds2 | prpplague: a computer on say a kayak |
| 23:20.06 | prpplague | ds2: there are plenty that can do that, but the price is pretty darn high |
| 23:20.16 | ds2 | where it may get slammed on a rock or get soaked |
| 23:20.21 | prpplague | ds2: in that case, you really don't need barcode scanner or mag stripe reader |
| 23:20.33 | prpplague | ds2: you are talking atleast $5k |
| 23:20.33 | ds2 | prpplague: I know but the more there is, the more likely the price will come down |
| 23:20.51 | prpplague | ds2: that's just it, they don't want the price to come down |
| 23:21.05 | ds2 | they as in "the man"? |
| 23:21.43 | prpplague | yea |
| 23:22.23 | *** join/#edev linac (n=lin@123.173.76.85) |
| 23:22.59 | ds2 | wonder if it is possible to modify an existing unit cheaply to meet those conditions - a pelican case, a refit of all buttons with a capacitive touch sensor(s) |
| 23:28.16 | MonMotha | ds2: what exactly do you want to do with the thing? |
| 23:28.27 | MonMotha | like how much CPU power and RAM do you require? |
| 23:30.16 | ds2 | MonMotha: I want the thing to survive... my daily use seems to be hard on PDAs |
| 23:30.30 | MonMotha | but what level of computational ability do you need? |
| 23:30.37 | MonMotha | full blown Linux, or just enough to run a small RTOS? |
| 23:31.12 | ds2 | full blown linux definitely |
| 23:31.28 | MonMotha | ok, then what I have in mind won't work |
| 23:31.38 | ds2 | something like a 400MHz PXA270 |
| 23:31.45 | MonMotha | I'm designing something at work that might otherwise meet your needs if you just needed an ARM7TDMI |
| 23:32.08 | ds2 | the pelican case + a refitted touch seems to be the easiest way |
| 23:32.16 | MonMotha | it's only IP65, but if your "immersion" is not prolonged, that is likely sufficient |
