| 00:54.36 | *** join/#edev dijenerate (n=dijenera@72.51.93.247) |
| 01:02.09 | *** join/#edev landley (n=landley@cpe-72-177-114-214.austin.res.rr.com) |
| 01:23.35 | flyback- | http://www.youtube.com/watch?v=OhnK5LdUCiQ# |
| 01:23.35 | flyback- | /msg j4k3 http://www.youtube.com/watch?v=u5MAFWaTteE# |
| 01:23.49 | flyback- | err |
| 01:23.51 | flyback- | wtf |
| 01:36.58 | cajaka | Has that ever worked for you? |
| 02:54.06 | *** join/#edev joe_bleau (n=joe_blea@adsl-69-152-210-234.dsl.fyvlar.swbell.net) |
| 03:04.44 | *** join/#edev FireEgl (i=FireEgl@Sebastian.FireEgl.Com) [NETSPLIT VICTIM] |
| 03:13.32 | *** join/#edev adyer (n=adyer@adsl-69-223-13-78.dsl.chcgil.ameritech.net) [NETSPLIT VICTIM] |
| 03:13.32 | *** join/#edev MothaWork_ (n=monmotha@149.164.193.61) |
| 03:13.32 | *** join/#edev cbrake_away (n=cbrake@oh-69-34-21-229.sta.embarqhsd.net) |
| 03:13.32 | *** join/#edev dbtid (i=qjgns0eb@cpe-71-72-252-171.columbus.res.rr.com) [NETSPLIT VICTIM] |
| 03:13.32 | *** join/#edev SpeedEvil (n=mauve@tor/regular/SpeedEvil) [NETSPLIT VICTIM] |
| 03:13.32 | *** join/#edev marty_p (i=1000@cp1292005-a.tilbu1.nb.home.nl) [NETSPLIT VICTIM] |
| 03:13.32 | *** join/#edev dfarnsworth (n=dfarnswo@65.200.49.156) [NETSPLIT VICTIM] |
| 03:33.31 | *** join/#edev dfarnsworth (n=dfarnswo@65.200.49.156) [NETSPLIT VICTIM] |
| 03:33.31 | *** join/#edev marty_p (i=1000@cp1292005-a.tilbu1.nb.home.nl) [NETSPLIT VICTIM] |
| 03:33.31 | *** join/#edev SpeedEvil (n=mauve@tor/regular/SpeedEvil) [NETSPLIT VICTIM] |
| 03:33.31 | *** join/#edev dbtid (i=qjgns0eb@cpe-71-72-252-171.columbus.res.rr.com) [NETSPLIT VICTIM] |
| 03:33.31 | *** join/#edev cbrake_away (n=cbrake@oh-69-34-21-229.sta.embarqhsd.net) [NETSPLIT VICTIM] |
| 03:33.31 | *** join/#edev MothaWork_ (n=monmotha@149.164.193.61) [NETSPLIT VICTIM] |
| 03:33.31 | *** join/#edev adyer (n=adyer@adsl-69-223-13-78.dsl.chcgil.ameritech.net) [NETSPLIT VICTIM] |
| 04:50.32 | *** join/#edev bbradley (n=bbradley@5ac8083e.bb.sky.com) |
| 06:21.11 | *** join/#edev DrZimmerman (n=theo@2001:5c0:8fff:fffe:0:0:0:6af1) |
| 06:57.01 | *** join/#edev redblue (i=star@ppp056.110-253-207.mtl.mt.videotron.ca) |
| 08:14.24 | *** join/#edev chouimat|away (n=dieu@r2351064.cidc.net) |
| 09:09.35 | *** join/#edev redblue (i=star@ppp095.108-253-207.mtl.mt.videotron.ca) |
| 09:55.53 | *** join/#edev chouimat|busy (n=dieu@r2351064.cidc.net) |
| 10:07.08 | *** join/#edev lyakh (n=lyakh@p57BD2922.dip0.t-ipconnect.de) |
| 10:42.12 | *** join/#edev steliosk (n=Stelios@ipa226.211.tellas.gr) |
| 11:14.49 | *** join/#edev linac (n=lin@121.41.53.24) |
| 11:47.40 | *** join/#edev hw_ (n=hw@p578b3905.dip0.t-ipconnect.de) |
| 12:19.41 | *** join/#edev T0mW (n=Tom@24.238.86.158.res-cmts.sth.ptd.net) |
| 13:27.04 | *** join/#edev prpplague (n=dave@mail.americanmicrosystems.com) |
| 14:07.57 | *** join/#edev hapchap_ (n=hapchap@mail.americanmicrosystems.com) |
| 14:13.36 | *** join/#edev dijenerate (n=dijenera@72.51.93.247) |
| 14:18.09 | *** join/#edev sjhill (n=sjhill@real.realitydiluted.com) |
| 14:45.40 | *** join/#edev GPSFan (n=kenm@12.10.255.246) |
| 14:45.40 | *** mode/#edev [+o GPSFan] by ChanServ |
| 14:49.15 | *** join/#edev JonHylands (n=hylandsj@CPE001c102333bd-CM0014e88f58e0.cpe.net.cable.rogers.com) |
| 14:56.49 | *** join/#edev chouimat|work (n=mchouina@64.26.181.250) |
| 14:57.36 | chouimat|work | morning |
| 15:20.06 | *** part/#edev JonHylands (n=hylandsj@CPE001c102333bd-CM0014e88f58e0.cpe.net.cable.rogers.com) |
| 15:47.20 | *** join/#edev sunrunner20 (n=jamesdoe@pool-71-170-40-114.dllstx.fios.verizon.net) |
| 15:55.29 | *** join/#edev CosmicPenguin (n=nobody@163.181.251.103) |
| 15:55.29 | *** mode/#edev [+o CosmicPenguin] by ChanServ |
| 16:18.02 | *** join/#edev ico2 (n=ico2@modem-1640.cougar.dialup.pol.co.uk) |
| 16:18.45 | prpplague | ho ho ho, merry freakin monday |
| 16:38.05 | adyer | cranky, are we? |
| 16:40.48 | sjhill | adyer: no, that's his normal greeting |
| 16:41.00 | sjhill | he's in a good mood today |
| 16:50.39 | chouimat|sick | hi |
| 16:51.49 | *** join/#edev sunrunner20 (n=jamesdoe@pool-71-170-40-114.dllstx.fios.verizon.net) |
| 16:53.06 | *** join/#edev sunrunner20|prom (n=jamesdoe@pool-71-170-40-114.dllstx.fios.verizon.net) |
| 16:54.17 | *** join/#edev sunrunner20 (n=jamesdoe@pool-71-170-40-114.dllstx.fios.verizon.net) |
| 17:00.03 | GPSFan | prpplague: morning.. did you build bluez for the hammer? and if so did you successfully integrate it into buildroot. I'm about to restart that project and have found a few people unsuccessfully integrating bluez into buildroot quite some time ago. |
| 17:03.21 | *** join/#edev samuelr (n=samuelr@dsl093-061-094.pit1.dsl.speakeasy.net) |
| 17:03.25 | hapchap_ | GPSFan: prpplague will be back in about an hour, but i dont think he ever integrated it into buildroot |
| 17:03.55 | GPSFan | hapchap_: ok, thanks, I'll see if I can. |
| 17:04.07 | hapchap_ | GPSFan: in fact, i am about to start doing just that for a product we have that uses the s3c2410 as well |
| 17:04.47 | GPSFan | hapchap_: well we can compare notes if either of us have any success. btw nice Xmas lite show... |
| 17:07.47 | hapchap_ | GPSFan: will do and thanks! |
| 17:21.11 | *** join/#edev FireEgl (i=FireEgl@Sebastian.Atlantica.CJB.Net) |
| 17:23.25 | *** join/#edev ico2 (n=ico2@modem-765.chimpanzee.dialup.pol.co.uk) |
| 18:05.36 | *** join/#edev redblue (i=star@ppp025.109-253-207.mtl.mt.videotron.ca) |
| 18:06.21 | *** join/#edev roxfan (i=dunno@234.216-64-87.adsl-dyn.isp.belgacom.be) |
| 18:18.24 | *** join/#edev lyakh (n=lyakh@p57BD2922.dip0.t-ipconnect.de) |
| 18:40.02 | prpplague | GPSFan: no i never used bluez thru buildroot |
| 18:40.08 | prpplague | GPSFan: had only just looked at it |
| 18:46.44 | GPSFan | prpplague: ok, well, I'm looking at integrating bluez-lib & bluez-util. hapchap_ said he was looking at doing the same. hopefully it will get done. |
| 19:08.39 | *** join/#edev ico2 (n=ico2@modem-765.chimpanzee.dialup.pol.co.uk) |
| 19:37.04 | *** join/#edev univac (n=univac@xmms2/user/univac) |
| 19:37.16 | *** part/#edev univac (n=univac@xmms2/user/univac) |
| 19:49.29 | *** join/#edev Crofton (n=balister@hc65217f1.dhcp.vt.edu) |
| 20:20.18 | *** join/#edev emil|k (n=emil@f054012018.adsl.alicedsl.de) |
| 20:35.28 | hapchap_ | i finally got the vids of my lights up on youtube |
| 20:35.49 | hapchap_ | here is christmas eve sarajevo (previously unseen): http://www.youtube.com/watch?v=revJ7Kccufg |
| 20:36.15 | hapchap_ | and the re-shot Mad Russian Christmas: http://www.youtube.com/watch?v=V5_GyEc_9GM |
| 20:42.21 | prpplague | hapchap_: whats the url for your flicker images? |
| 20:45.56 | prpplague | http://www.elinux.org/Xmas_Video |
| 20:45.59 | prpplague | hapchap_: http://www.elinux.org/Xmas_Video |
| 20:47.29 | hapchap_ | prpplague: see if this works http://www.flickr.com/photos/21836722@N02/sets/72157603459882107/ |
| 20:47.40 | prpplague | hapchap_: yea i found it |
| 20:49.20 | prpplague | hapchap_: you post more info on the wiki page if you want(and have time) |
| 20:49.52 | hapchap_ | prpplague: i will try to find time... i really do want to get it all organized |
| 20:51.17 | prpplague | hapchap_: hehe, np, trust me, i know how you feel |
| 20:51.35 | prpplague | hapchap_: there is a ton of stuff i need to do for the hammer, but all the office stuff has me down |
| 20:52.35 | hapchap_ | prpplague: is rusty still using his aml email? |
| 20:54.10 | prpplague | hapchap_: probably, but you may want to use his home account |
| 20:54.12 | prpplague | one sec |
| 20:55.01 | *** mode/#edev [+o prpplague] by ChanServ |
| 20:57.03 | *** join/#edev JonHylands (n=hylandsj@CPE001c102333bd-CM0014e88f58e0.cpe.net.cable.rogers.com) |
| 21:03.01 | JonHylands | Hey prpplague, any word on that eval kit? |
| 21:13.39 | prpplague | JonHylands: yea, spoke to the boss about it |
| 21:13.59 | prpplague | JonHylands: probably ship to you this week |
| 21:14.06 | JonHylands | okay, cool |
| 21:14.32 | wmat | prpplague: speak to him about shiipping to canada :) |
| 21:14.41 | prpplague | wmat: ? |
| 21:14.52 | JonHylands | heh - just make sure you send it USPS, and not UPS Ground |
| 21:15.14 | JonHylands | Fedex will work okay as well |
| 21:15.38 | prpplague | JonHylands: oh? we'd setup for most international stuff to be USPS, but we had canada setup for UPS |
| 21:16.00 | JonHylands | ugh - please don't do UPS - I will end up paying $50-60 in brokerage fees |
| 21:16.03 | wmat | prpplague: just teasing you. I thought that was your excuse for not sending me one ;) |
| 21:16.28 | prpplague | wmat: hehe, it was at the time |
| 21:16.38 | prpplague | wmat: our original betas weren't RoHS |
| 21:16.45 | *** join/#edev T0mW (n=Tom@24.238.86.158.res-cmts.sth.ptd.net) |
| 21:16.48 | wmat | prpplague: oh right, that was it |
| 21:16.56 | T0mW | prpplague: hey, there you are |
| 21:16.59 | prpplague | wmat: thats why it was limited to US |
| 21:17.52 | wmat | prpplague: the boss told me today I could order toys so long as I add their support into our stuff, so I'll see about ordering a kit |
| 21:18.06 | wmat | prpplague: what's the URI again? |
| 21:18.20 | prpplague | wmat: http://www.tincantools.com |
| 21:18.40 | prpplague | wmat: the kit is a good buy |
| 21:19.17 | prpplague | JonHylands: we are collecting info right now on what people will want for a robotics carrier board |
| 21:20.54 | *** join/#edev davidc__ (n=davidc__@S01060002b360aacd.vc.shawcable.net) |
| 21:21.00 | prpplague | davidc__: greetings |
| 21:21.16 | prpplague | davidc__: have you started begging in the streets yet? |
| 21:21.44 | davidc__ | ay prpplague |
| 21:21.46 | davidc__ | :P |
| 21:21.48 | davidc__ | bah.. too bad you're the one opped or I'd make you regret that ;) |
| 21:22.00 | prpplague | hehe |
| 21:23.10 | davidc__ | mmh.. the only begging I've been doing has been to the powerpc kernel gods to smote all that is the DHT-walnut boards |
| 21:23.13 | davidc__ | damn thing is being a PITA |
| 21:23.53 | davidc__ | *smite |
| 21:24.07 | prpplague | davidc__: hehe |
| 21:24.58 | davidc__ | prpplague: I bought 5 of em to use for misc projects.. but the 2.6.24-rc5 kernel is being irritating on them.. kept on oopsing, so I enabled all the debug settings in the kernel, and now it doesn't feel like booting >:( |
| 21:25.14 | prpplague | doh |
| 21:25.40 | prpplague | davidc__: i've not done much with mips, i had planned on getting some of those walnut boards when they were cheap |
| 21:25.49 | prpplague | davidc__: but i was very busy at the time and they sold out |
| 21:25.57 | davidc__ | prpplague: theyre ppc |
| 21:26.09 | prpplague | davidc__: duh, yea, thats whay i meant to say |
| 21:26.22 | davidc__ | prpplague: I'm actually fairly sure the oopsing issue is due to how the NFS root was mounted, but now I've gotta figure out how to config the kernel so it'll boot again |
| 21:26.26 | prpplague | davidc__: i was writing something up about mips when i switched this screen |
| 21:26.32 | davidc__ | prpplague: heh |
| 21:27.07 | davidc__ | prpplague: I'm playing with it mostly because I gotta learn the PPC ISA for a virtex FX12 based board I'm getting [has a powerpc core inside the FPGA} |
| 21:28.10 | davidc__ | oh, and also because I want to use the jack audio router to make my living room speakers a virtual pair of speakers from the comp ;) |
| 21:29.24 | *** join/#edev ico2 (n=ico2@modem-765.chimpanzee.dialup.pol.co.uk) |
| 21:29.58 | prpplague | davidc__: hehe |
| 21:30.06 | prpplague | davidc__: fpga with a ppc core? |
| 21:30.08 | *** join/#edev anon (n=fynlwzo@200.241.202.111) |
| 21:30.10 | davidc__ | prpplague: yup |
| 21:30.11 | prpplague | davidc__: that sounds expensive |
| 21:30.18 | davidc__ | prpplague: they're ~100 bucks |
| 21:30.25 | davidc__ | prpplague: but the board is 300 from Xilinx |
| 21:30.30 | davidc__ | prpplague: and they're fairly powerful |
| 21:30.39 | davidc__ | [got a few GIGE MAC's onboard too] |
| 21:30.43 | anon | somebody kwons about Busybox?!? i have a problem |
| 21:31.02 | prpplague | davidc__: $100 per chip or per board? |
| 21:31.10 | prpplague | anon: ask your question |
| 21:31.20 | anon | How do I change the space of device to resolve this problem: "No space left on device" ??, on busybox...?, |
| 21:31.27 | davidc__ | anon: thats not a busybox problem |
| 21:31.35 | anon | i´m using the command wget |
| 21:31.37 | anon | ? |
| 21:31.42 | adyer | anon why don't you pick one channel and stop spamming multiple channels |
| 21:31.55 | davidc__ | anon: that means you have no space left on the disk |
| 21:31.57 | anon | because i´m a bad boy :D |
| 21:32.08 | davidc__ | anon: busybox is just a piece of software |
| 21:32.15 | anon | humm |
| 21:32.44 | prpplague | anon: try doing a df |
| 21:32.47 | anon | [davidc__]: ok, however, can i change the space? |
| 21:32.52 | prpplague | anon: to list your available space |
| 21:32.52 | davidc__ | prpplague: the chips are ~100, board is ~300, but thats in single QTY |
| 21:33.00 | davidc__ | anon: put a new hard disk in? |
| 21:33.03 | anon | ok |
| 21:33.11 | prpplague | delete old files? |
| 21:33.20 | davidc__ | anon: how would you give any computer more disk space |
| 21:33.35 | anon | df = >>> /dev/root 5402 4714 409 92% / |
| 21:33.47 | hapchap_ | anon: inode count too low? |
| 21:34.05 | davidc__ | anon: do df -h, we don't know the sector size |
| 21:34.58 | anon | [davidc__]: is the same thing |
| 21:35.07 | davidc__ | anon: do a mount |
| 21:35.22 | prpplague | davidc__: older busybox df doesn't support the -h |
| 21:35.33 | davidc__ | prpplague: ah, heh |
| 21:35.35 | anon | [prpplague]: yes I use -k |
| 21:35.43 | anon | what´s a mount? |
| 21:35.47 | davidc__ | run "mount" |
| 21:35.50 | davidc__ | and give us the results |
| 21:35.54 | anon | # mount |
| 21:35.54 | anon | /dev/root on / type ext2 (rw) |
| 21:35.54 | anon | none on /proc type proc (rw) |
| 21:36.12 | prpplague | basically you only have about 400k of space available |
| 21:36.23 | anon | yes... ;( |
| 21:36.25 | prpplague | and what ever you are trying to wget is bigger than 400k |
| 21:36.28 | anon | can I change this? |
| 21:36.29 | davidc__ | yup, and its a writeable FS |
| 21:36.48 | anon | [prpplague]: i would like to change this limit |
| 21:37.09 | prpplague | anon: again, the limit is based on the storage capacity of the device |
| 21:37.16 | adyer | peeerhaps he could etch a few more cells onto his flash die :-) |
| 21:37.27 | prpplague | anon: the only way to change it is to add more, or delete files |
| 21:37.29 | davidc__ | adyer: sounds like a good idea |
| 21:37.30 | anon | [prpplague]: device = hard disk? |
| 21:37.32 | prpplague | hehe |
| 21:37.39 | davidc__ | anon: depends on the device |
| 21:37.48 | prpplague | anon: it could be flash, ram, hard disk |
| 21:37.57 | prpplague | anon: could be just about anything |
| 21:38.09 | hapchap_ | prpplague: it couldnt be cheese |
| 21:38.13 | anon | [davidc__]: is a comand to see the space of a file, directoryu?!?! |
| 21:38.19 | hapchap_ | prpplague: or could it.... hmmmm.... |
| 21:38.24 | prpplague | hapchap_: hmm, now that is interesting |
| 21:38.37 | prpplague | hapchap_: you could burn small black dots on cheese with a laser |
| 21:38.52 | prpplague | hapchap_: then use a photo sensor to read it back |
| 21:38.54 | hapchap_ | prpplague: i getting the patent paperwork now |
| 21:38.55 | anon | what´s the command to see the space of a file?! |
| 21:38.58 | davidc__ | anon: du |
| 21:39.02 | davidc__ | anon: or ls |
| 21:39.02 | hapchap_ | prpplague: were going to be rich! |
| 21:39.15 | anon | [davidc__]: ls is to see he files |
| 21:39.21 | davidc__ | anon: rtfm |
| 21:39.22 | prpplague | hapchap_: use standard cheese slices that in plastic wrap |
| 21:39.31 | hapchap_ | prpplague: hehe |
| 21:39.38 | anon | i want the SPACE it´s using |
| 21:39.44 | prpplague | anon: du |
| 21:39.45 | anon | the du do not exist |
| 21:39.54 | prpplague | anon: then try using ls -al |
| 21:40.24 | prpplague | anon: we generally like to help people, but you are pushing the limit of our patience |
| 21:40.35 | davidc__ | hapchap_: with the artificiality of that processed cheese, you may have just invented a new long-term storage medium |
| 21:40.46 | davidc__ | hapchap_: data density might be a problem, but it'll last forever |
| 21:41.09 | hapchap_ | davidc__: so long DVD, HELLO LIMBURGER! |
| 21:41.31 | davidc__ | hapchap_: nah, you gotta use the plastic wrapped processed cheese slices |
| 21:41.32 | anon | [prpplague]: thx! |
| 21:41.52 | davidc__ | hapchap_: otherwise the actual real cheese contents will cause problems |
| 21:41.58 | hapchap_ | davidc__: those would be the portable version... internal drives would be blocks of velveeta |
| 21:42.20 | prpplague | hehe |
| 21:42.29 | adyer | total space on his device is about 5M, so 'm guessing flash on a router |
| 21:42.29 | davidc__ | hapchap_: hmm.. you could have WORO media by stacking slices together + compressing |
| 21:42.39 | davidc__ | hapchap_: and using a cheese slicer to access the old data |
| 21:42.46 | davidc__ | er, stacked data |
| 21:43.16 | hapchap_ | davidc__: hehe i love it! |
| 21:43.16 | adyer | lasering cheese is actaully a difficult problem, tends to burn |
| 21:43.29 | anon | huumm... busy box run linux programs?!?! |
| 21:43.34 | davidc__ | adyer: thats the idea. |
| 21:43.46 | adyer | somebody spent about a year coming up with a laser to cut cheese into shapes without burning it |
| 21:43.46 | davidc__ | anon: busybox is just a single multicall binary that implements standard utilities. |
| 21:43.57 | hapchap_ | anon: busybox is a linux program |
| 21:43.58 | davidc__ | adyer: the idea is to burn black spots onto it for data storage |
| 21:44.22 | anon | i run a program and it shows a error... but this program never do this |
| 21:44.35 | davidc__ | head => desk |
| 21:44.40 | adyer | methinks our visitor is probably mucking with firmware on a router cause it's so 37337 |
| 21:44.41 | prpplague | hehe |
| 21:44.54 | davidc__ | anon: define program, error, this program, and "this" |
| 21:45.08 | anon | [davidc__]: 1: Syntax error: "(" unexpected |
| 21:45.10 | *** mode/#edev [+o davidc__] by prpplague |
| 21:45.16 | adyer | i would suggest using something with a lower water content, perhaps parmesan |
| 21:45.18 | anon | i´m change the distro |
| 21:45.20 | prpplague | davidc__: for when you get tired |
| 21:45.29 | davidc__ | anon: sounds like you're trying to use an i386 binary on arm / etc |
| 21:45.45 | adyer | shell code failing in ash |
| 21:45.56 | adyer | prolly written for bash |
| 21:46.06 | davidc__ | adyer: ash will try and run i386 executables :P |
| 21:46.14 | davidc__ | adyer: gives that exact error [just saw it yesterday eve] |
| 21:46.26 | hapchap_ | usually says something about a "(" methinks |
| 21:46.41 | prpplague | ok, so a standard slice is about 3.25", if do a .05" dot with .05" spacing you get 32 bits |
| 21:47.16 | davidc__ | prpplague: nah, 32 x 32 |
| 21:47.27 | davidc__ | prpplague: why limit yourself to 1d |
| 21:47.28 | prpplague | for a total of about 32x32=1024 per slice |
| 21:47.31 | adyer | encode the data in braille |
| 21:47.32 | davidc__ | ah, :P |
| 21:48.26 | adyer | backup readers come cheap, but you might lose data if they're hungry |
| 21:48.33 | prpplague | HA |
| 21:48.56 | hapchap_ | heat is going to be an issue... "holy crap! my drive melted!" |
| 21:48.57 | davidc__ | prpplague: you'd lose some bits to the Spurious eRratum Error Alternative Databits |
| 21:48.59 | prpplague | hapchap_: so you store about 128 bytes with a rudimentry config |
| 21:49.04 | davidc__ | [aka, the cheese SPREAD system] |
| 21:49.09 | prpplague | hehe |
| 21:49.13 | hapchap_ | davidc__: hehe |
| 21:49.54 | adyer | might be able to store multiple bits per cell with controlled burn rate |
| 21:49.58 | prpplague | davidc__: my all time favorite is of course my adding machine paper-roll tape reader/writer |
| 21:50.13 | prpplague | davidc__: 9 bits per line |
| 21:50.21 | prpplague | davidc__: 1 being a clock the rest data |
| 21:50.53 | prpplague | T0mW: so whats up with the DMA issue? |
| 21:51.35 | prpplague | hapchap_: iirc 3M did a storage device using a roll of packing tape in a similiar manner |
| 21:51.54 | prpplague | hapchap_: addjusting the focus of the laster, they were about to burn dots on individual layers |
| 21:51.58 | T0mW | prpplague: ok, the kernel + patches you distro'ed for Hammer seem to be "mainline"? Where it looks to be that OpenMoko is diverging the DMA interface along the lines that Thomas Klefener is using? |
| 21:52.31 | prpplague | T0mW: yea, i tend to use as close to linus and rmk patches as possible |
| 21:52.42 | T0mW | prpplague: I was looking at getting the MCI interface working and got slammed into two different DMA API approaches |
| 21:53.18 | prpplague | T0mW: ahh |
| 21:54.20 | prpplague | T0mW: well i'm working on a release of 2.6.24-rc5 that has the sd/mmc via spi |
| 21:54.20 | prpplague | T0mW: however there are a ton of problems |
| 21:54.20 | prpplague | T0mW: first and formost is the s3c24xx spi driver is broken in several places |
| 21:54.26 | T0mW | prpplague: it looks as if the S3C24xx MCI implementation uses a DMA api which is more along the lines of manually moving things along: start, poll for completion, close. The Hammer stuff appears to use a "more elegant" approach of data structures. |
| 21:54.31 | prpplague | T0mW: the other is the sd/mmc driver via spi has some control issues that aren't working well with the spi driver |
| 21:54.48 | prpplague | T0mW: just as reminder |
| 21:55.08 | prpplague | T0mW: the MCI driver you are probably looking at is via the sdio controler, not the SPI interface |
| 21:55.19 | T0mW | I'm not even going there with SPI. On that board I showed you, I'm using the SDATA[0..4], MCI, interface. |
| 21:55.27 | T0mW | correct |
| 21:55.47 | prpplague | ahh ok |
| 21:56.31 | T0mW | prpplague: at first, I didn't think your kernel had any DMA arch in it, then I read more into the sound code and saw that the i2s and pcm drivers do use DMA and appear to be functional? |
| 21:56.50 | T0mW | prpplague: is the DMA operational in your patches? |
| 21:57.07 | T0mW | just need to confirm that. |
| 21:57.12 | anon | argh what menas this erro " 1: Syntax error: "(" unexpected " |
| 21:57.17 | prpplague | T0mW: i could not say, as the hammer does not have i2s or pcm, so they have never been tested |
| 21:57.22 | T0mW | I hate to diverge from the mainstream by using OpenMoko |
| 21:58.05 | ds2 | branching is fun! |
| 21:58.10 | prpplague | anon: it means that you are more than likely trying to execute an application compiled for another platform or you have a shell script that has incorrect end of line formating, i.e. you copied it from a winblows box |
| 21:58.11 | hapchap_ | anon: yes, that is the error you will get when trying to run i386 binaries on ARM |
| 21:58.16 | T0mW | I look in arch/arm/mach-s3c2410 and arch/arm/platform-s3c2410 and there is files called "dma.c", but I cannot see how they could possibly work. |
| 21:58.31 | ds2 | everyone should go off and spend days merging things between different vendor/project branches ;) |
| 21:58.51 | adyer | ds2 branching is fun, but merging is a b**** |
| 21:59.01 | T0mW | prpplague: I thought that you might have had some insight into that. Maybe the 2.6.22 doesn't have a functional DMA arch for the Samsung chips, as yet? |
| 21:59.19 | anon | [prpplague]: platform is Cent0S, Debian ?! |
| 21:59.26 | prpplague | T0mW: there is a functional DMA as far back as 2.6.16 |
| 21:59.29 | prpplague | T0mW: we use it for several items |
| 21:59.39 | prpplague | T0mW: just not with i2s as of yet |
| 21:59.45 | ds2 | adyer: what SCM are you using? |
| 21:59.50 | T0mW | prpplague: yeah, but it is a different archetecture than what I see in 2.6.22 |
| 22:00.04 | adyer | ds2 git and sneakernet |
| 22:00.08 | prpplague | T0mW: best thing to do is go to the patch system at arm.linux.org.uk and do a search for s3c24xx |
| 22:00.12 | T0mW | It may have been that they revamped it since 2.6.16 |
| 22:00.22 | adyer | ds2 trying to get everyone on git for kernel |
| 22:00.25 | prpplague | T0mW: indeed been has been working over the platform files |
| 22:00.31 | ds2 | adyer: is it really easier with git? |
| 22:00.32 | prpplague | T0mW: originally it was just for the 2410 |
| 22:00.37 | prpplague | T0mW: then 2440 was added |
| 22:00.54 | prpplague | T0mW: then all the 2412/2413/2460/24a0 were all being added |
| 22:00.55 | adyer | ds2 not unitl everyone uses it! i'm not an expert, just starting |
| 22:00.59 | prpplague | T0mW: it was becomeing a mess |
| 22:01.02 | T0mW | prpplague: I saw something like that: the 2442 ? |
| 22:01.20 | prpplague | T0mW: so benn reworked the structure and started adding patches |
| 22:01.30 | T0mW | great |
| 22:01.36 | prpplague | T0mW: the complete rework probably won't be finished untill 2.6.25 |
| 22:01.42 | T0mW | so, we might be in the middle of "work in progress" |
| 22:01.50 | prpplague | T0mW: most it will be complete as of 2.6.24 |
| 22:02.07 | prpplague | T0mW: indeed, there are a number of subsystems that are being "tweaked" right now |
| 22:02.24 | prpplague | T0mW: including the spi subsystem along with the sd/mmc and sdio interfaces |
| 22:02.32 | T0mW | ok, at this point, I think that I am going to have to diverge and use the OpenMoko DMA structuring / kernel source. |
| 22:03.10 | T0mW | I hate doing that as then I would have to merge at some point and do a rewrite |
| 22:03.14 | prpplague | T0mW: right now, my suggestion is to use what works and takes the least amoung of time to get working |
| 22:03.29 | prpplague | T0mW: then when 2.6.24 or 2.6.26 comes out, do an upgrade |
| 22:03.43 | davidc__ | anyone here debugged a powerpc kernel oops before? |
| 22:03.44 | T0mW | :) |
| 22:04.46 | prpplague | not i |
| 22:04.53 | prpplague | davidc__: iirc agaffney and jbevren might have |
| 22:05.25 | T0mW | davidc__: at one time, I was thinking of chasing a panic. It is quite involved as you have to run the kernel using an external debugger that can find out where the memory is being used. |
| 22:05.31 | *** part/#edev JonHylands (n=hylandsj@CPE001c102333bd-CM0014e88f58e0.cpe.net.cable.rogers.com) |
| 22:05.39 | davidc__ | T0mW: or add shitloads of kprintfs ;) |
| 22:05.46 | T0mW | yeah, but |
| 22:06.07 | T0mW | something keeps saying ksyms or kdebug |
| 22:06.37 | T0mW | it's been a few years since I was crazy enough to consider doing something like that. |
| 22:06.39 | davidc__ | my other problem is Kallsyms doesn't work nicely on this board, or the decompression stage goes bonkers |
| 22:06.55 | T0mW | yeah, I think that is the track you need to be on. |
| 22:06.56 | ds2 | a software controlled LED can be better then printk but that isn't universally available :( |
| 22:07.09 | prpplague | davidc__: so you aren't getting a clean decompression? |
| 22:07.17 | davidc__ | prpplague: only if the kernel size is too big ;) |
| 22:07.27 | T0mW | so, dump it |
| 22:07.29 | ds2 | btw, anyone here messed with the mediamvp stuff before? |
| 22:07.32 | davidc__ | prpplague: it decompresses fine with a smaller kernel size, but kallsyms goes to big ) |
| 22:07.42 | prpplague | davidc__: interesting |
| 22:07.46 | davidc__ | ds2: I got a SW controlled LED, but the serial conn for printk works fine |
| 22:08.11 | ds2 | davidc__: weird things happen to printk's during boot up; they seem to get buffered waiting for serial init |
| 22:08.11 | prpplague | davidc__: yea, i'd enable printascii, and shove one in printk.c |
| 22:08.30 | davidc__ | ds2: eh, its booting fine |
| 22:08.30 | T0mW | davidc__: at one time, I dumped parts of the kernel memory using printk, captured it via minicom, then processed the ascii file... brute force. |
| 22:08.32 | adyer | ds2 that's how its supposed to work |
| 22:08.35 | prpplague | davidc__: thats the first thing i do with a fresh kernel |
| 22:08.56 | T0mW | took a while, but I found my prob |
| 22:09.00 | davidc__ | ds2: the oopses happen only when I use the alsa subsystem, but the oopses are showing up in the VM subsystem :/ |
| 22:09.03 | ds2 | adyer: I know which is why I sometimes want a sw controlled LED so I can catch stuff before the serial stuff gets setup |
| 22:09.10 | prpplague | davidc__: ahh |
| 22:09.29 | prpplague | davidc__: you get any BUG() warnings? |
| 22:09.34 | davidc__ | prpplague: not that |
| 22:09.35 | ds2 | or when you are messing with clocks and manage to mess up the UART clocks ;) |
| 22:09.38 | davidc__ | er, that I've seen |
| 22:09.42 | adyer | ds2 if you have a jtag connection you can usually dump the printk buffer before serial is up |
| 22:10.02 | prpplague | davidc__: you might add some code to the BUG() call |
| 22:10.05 | davidc__ | eh.. I'm tempted just to make myself a debugger for this board.... just need to find a powerpc OCD + hack on it to talk to the jtag HW I have |
| 22:10.25 | prpplague | davidc__: you might find that you are getting a BUG() called which is normally generates an oops |
| 22:10.30 | ds2 | adyer: heh.. I been stuck on omap... docs are scarce :( |
| 22:10.30 | davidc__ | kk |
| 22:11.06 | davidc__ | prpplague: know where that macro is defined? grep isn't being particularly helpful |
| 22:11.19 | adyer | ds2 I grouse about omap every time I see our TI guy. Nice parts, but too many cell phone only parts |
| 22:11.37 | anon | SphereServer-0.56b-200706021830-Linux.tgz |
| 22:11.37 | prpplague | davidc__: should be in something like include/asm-powerpc/bug.h |
| 22:11.54 | adyer | http://lxr.linux.no/source/ is good for finding kernel stuff |
| 22:12.06 | ds2 | adyer: I'll leave that problem up to the non engineers. I just need docs. |
| 22:12.14 | T0mW | prpplague: btw, thanks for your input on the DMA issue, appreciate that. |
| 22:12.22 | prpplague | T0mW: np |
| 22:12.47 | prpplague | T0mW: sorry i can't be of more assitance, but right now between 2.6.22 and 2.6.26 is going to be rough time for some parts of the s3c24xx |
| 22:12.56 | hapchap_ | can i embed youtube vids on elinux.org? doesn't look like mediawiki allows it by default |
| 22:13.09 | T0mW | prpplague: I see the AML M5900 in there |
| 22:13.26 | prpplague | hapchap_: might pester wmat he does the maintaince |
| 22:13.31 | prpplague | wmat: ping ping |
| 22:13.38 | prpplague | T0mW: hehe, in where? |
| 22:13.46 | T0mW | prpplague: OpenMoko |
| 22:13.58 | prpplague | T0mW: uh? what? |
| 22:14.13 | prpplague | hapchap_: did you? |
| 22:14.36 | prpplague | T0mW: it say who added it? |
| 22:14.57 | T0mW | Say Y here if you are using the American Microsystems M5900 Series |
| 22:15.33 | T0mW | <PROTECTED> |
| 22:15.33 | T0mW | <PROTECTED> |
| 22:15.38 | T0mW | heh |
| 22:15.47 | T0mW | prpplague: you don't even know what you are doing anymore! |
| 22:16.25 | prpplague | T0mW: are you sure you aren't looking at the kernel config? |
| 22:17.39 | T0mW | prpplague: it's in there: arch/arm/mach-s3c2410/mach-amlm5900.c |
| 22:17.59 | prpplague | T0mW: right, the M5900 is in the main kernel tree |
| 22:18.20 | prpplague | T0mW: but we didn't add anything to OE |
| 22:18.22 | T0mW | prpplague: ah, just had that same thought, I need a break |
| 22:18.24 | davidc__ | anyhow - this is the oops I'm getting... http://pastie.caboo.se/129761 [just if anyone feels really bored] |
| 22:19.22 | davidc__ | the double call trace bit has me a bit confused |
| 22:19.31 | prpplague | davidc__: thats interesting |
| 22:19.40 | prpplague | davidc__: don't believe i've ever seen that before |
| 22:19.42 | davidc__ | yeah, my thoughts exactly ;) |
| 22:19.57 | prpplague | davidc__: "kernel access of bad area" |
| 22:20.12 | T0mW | prpplague: oh, I ordered another Hammer board. I think I broke the one I have: VD5 is floating on the LCD interface |
| 22:20.13 | prpplague | davidc__: kinda sounds like it's be "violated" |
| 22:20.24 | davidc__ | yup, so its deferencing some weird pointer |
| 22:20.24 | T0mW | s/VD5/VD4 |
| 22:20.36 | prpplague | T0mW: doh, how did that happen? |
| 22:23.05 | T0mW | prpplague: that I cannot figure out, I didn't power the Hammer with the LCD when I had the pinout backward. Might be that it was broken when I got it. |
| 22:23.20 | T0mW | prpplague: whatever, $150 isn't going to break me. |
| 22:25.14 | T0mW | prpplague: <sigh> sometimes I am working too fast and don't take time to see what I'm doing, I prolly broke it and didn't even know it. heh |
| 22:27.01 | prpplague | T0mW: i'm make a note to run a couple of tests on some straight out the box to see if there is problem |
| 22:27.19 | prpplague | T0mW: normally we test them but toggling leds on each of the gpio lines |
| 22:28.05 | prpplague | T0mW: hey, did you look at the bat charger circuit i posted? |
| 22:28.11 | T0mW | prpplague: no |
| 22:28.18 | prpplague | T0mW: http://www.elinux.org/Lithium_Ion_Charger |
| 22:30.18 | T0mW | prpplague: yeah, microchip makes some nice stuff |
| 22:30.36 | prpplague | T0mW: tincantools is thinking of selling that as module |
| 22:30.40 | T0mW | I use their MIC series of regulators |
| 22:30.55 | prpplague | yea good stuff |
| 22:30.58 | prpplague | we use them as well |
| 22:31.12 | T0mW | MIC4680YM is a favorite of mine |
| 22:31.21 | T0mW | 1Amp switcher |
| 22:31.29 | prpplague | T0mW: oh i got those chrontel samples in |
| 22:33.13 | davidc__ | T0mW: if we're talking micrel switching favorites, mine is the MIC2169AY |
| 22:33.19 | T0mW | prpplague: chrontel seems to strike me as a small specialty mfgr? |
| 22:33.23 | davidc__ | but I can't source it anywhere in reasonable qty |
| 22:33.56 | prpplague | T0mW: indeed, these video chips are very specialized |
| 22:36.05 | T0mW | davidc__: ooo! You go for the big-current, eh? |
| 22:36.22 | davidc__ | T0mW: needed 3A, and I could use tiny fets.. |
| 22:36.31 | davidc__ | 3 A, really smooth output, ~1 sq inch |
| 22:36.34 | T0mW | davidc__: I like to keep it under an Amp, heh |
| 22:47.11 | adyer | davidc__ looks pretty generic, and I hate current sense using the fets |
| 22:47.37 | davidc__ | adyer: yeah, its a generic one, but its cheap, fast, and has excellent voltage regulation |
| 22:47.55 | davidc__ | at least in my experience ;) |
| 22:59.53 | adyer | davidc__: check out fan2103 (integrated fets and powergood output) |
| 23:03.43 | *** join/#edev CosmicPenguin (n=nobody@163.181.251.103) |
| 23:03.43 | *** mode/#edev [+o CosmicPenguin] by ChanServ |
| 23:04.29 | *** join/#edev ico2 (n=ico2@modem-765.chimpanzee.dialup.pol.co.uk) |
| 23:07.53 | *** join/#edev landley (n=landley@cpe-72-177-114-214.austin.res.rr.com) |
| 23:08.36 | landley | Anybody currently online have a hammer board? |
| 23:08.46 | landley | I have a couple of questions about the "flyswatter" thing. |
| 23:08.48 | davidc__ | you just missed prpplague ;) |
| 23:09.05 | landley | 1) Which way does the cable connect to the actual arm chip thingy on the simm board? |
| 23:09.21 | landley | I'm used to the red stripe going next to the "1", but there's no "1" on the pins. |
| 23:09.33 | landley | I'm guessing that the cable is going away from the chip, but it's 50/50. It fits both ways. |
| 23:09.53 | landley | It's quite possible I've just plugged it in the wrong way, powered it on, and destroyed my hammer and/or flyswatter. |
| 23:10.00 | landley | This brings me to my second question: |
| 23:10.10 | landley | When the flyswatter is plugged into USB, it shows up as two serial devices. |
| 23:10.19 | landley | Which one's the console, and which one's the jtag? |
| 23:11.16 | landley | I tried both and got no response the way I did using a USB/serial converter to talk to the actual board. |
| 23:11.43 | landley | Possibly the linux kernel's console is still talking to the built-in serial port, and this one just has nothing hooked up to it. |
| 23:12.06 | landley | If there's documentation for any of this, it wasn't on the CD that came with the board, nor is it obviously linked from the hammer web pages I was sent to. |
| 23:15.34 | hapchap_ | landley: the two serial ports are exaclty that, two serial ports... one is the external serial port on the board and the other is the jtag |
| 23:17.43 | *** join/#edev prpplague (n=dave@mail.americanmicrosystems.com) |
| 23:18.06 | prpplague | landley: hey |
| 23:18.12 | prpplague | landley: jsut about to leave for the day |
| 23:18.14 | landley | I've been asking questions about the hammer. |
| 23:18.23 | landley | 1) Which way do I connect the flyswatter cable? |
| 23:18.30 | landley | There's no "1" that the red stripe goes next to. |
| 23:18.43 | landley | (And if I guessed the wrong way, did I blow out the board?) |
| 23:19.18 | landley | 2) There are two serial ports, one jtag and one a serial port on the board. How do I tell which is /dev/ttyUSB0 and which is /dev/ttyUSB1? |
| 23:19.19 | prpplague | landley: if you look at the silkscreen you will see a diag mark on the board, its the side with VD0 marked on the board |
| 23:19.47 | landley | Also, there's no console What's a diag mark? |
| 23:19.58 | landley | VD0 is the pin that normally has a "1" next to it, then? |
| 23:20.17 | landley | 3) Is the kernel going to put a console on the flyswatter serial port, if it's already got /dev/console on the built-in serial port? |
| 23:20.39 | landley | I tried talking to it and got nothing. |
| 23:20.57 | prpplague | landley: ok lets start with just the jtag portion |
| 23:21.45 | landley | ok... |
| 23:21.49 | prpplague | landley: with the hammer board in the carrier, locate on the carrier board the VD0 pin |
| 23:22.02 | landley | Ah, it's labeled on the _carrier_. Right... |
| 23:22.08 | landley | I was looking on the hammer thingy itself. |
| 23:22.18 | prpplague | landley: ok that is the side the pin one is on the jtag |
| 23:22.28 | landley | Right, I had it guessed the right way. |
| 23:22.39 | prpplague | landley: if you look at the side of the 2x7 header a slight / is marked on the silkscreen |
| 23:22.51 | prpplague | landley: we are marking it better in rev2 of the board |
| 23:23.40 | landley | I don't see a slash, but VD0 is on the carrier, ok. |
| 23:23.49 | landley | So, it's plugged in and powered on. |
| 23:24.08 | landley | I'd like to be able to use it as a ubs/serial converter, like you said it could be. |
| 23:24.22 | prpplague | landley: ok, next, connect the rs-232 cable from the db9 on the carrier to the db9 on the flyswatter |
| 23:25.28 | landley | Which way does it plug in on the flyswatter? |
| 23:25.41 | landley | I have it with the cable dangling off the edge of the board. |
| 23:26.19 | landley | This ribbon cable is an rs232 cable, right? |
| 23:26.31 | landley | For some reason I thought rs232 was printer cable... |
| 23:26.33 | prpplague | landley: sorry, no that is the jtag cable |
| 23:26.39 | *** join/#edev Redhatter (n=stuartl@gentoo/developer/redhatter) |
| 23:26.54 | landley | Ah! |
| 23:27.00 | prpplague | landley: your package should have included a cable with a db9 female on one end and a db9 male on the other |
| 23:27.09 | landley | So flyswatter acts as USB to serial converter when it's not plugged into the jtag. |
| 23:27.28 | prpplague | landley: actually it does both |
| 23:27.29 | landley | Right, I thought the jtag cable would make a serial port show up to the arm processor. |
| 23:27.40 | prpplague | landley: ahh, no |
| 23:28.14 | landley | Ok, the flyswatter serial port won't plug directly into the hammer carrier serial port. |
| 23:28.23 | landley | There are mounting hex nuts in the way, with no obvious way to remove them. |
| 23:28.31 | prpplague | landley: it's better to think of the flyswatter as two devices on one board, a usb->jtag and a usb->rs-232 |
| 23:28.32 | landley | You sent me an extender cable, lemme see if I can find it... |
| 23:28.43 | prpplague | landley: correct, there should be cable |
| 23:29.04 | prpplague | landley: yea, i've started doing docs, just haven't been able to post them yet |
| 23:29.30 | prpplague | landley: gonna takes some pictures tomorrow for the wiki |
| 23:31.09 | landley | Total sphagetti. |
| 23:31.18 | landley | My flyswatter is upside down due to the serial cable pulling on it. |
| 23:32.00 | prpplague | landley: yea, most people will screw it down to something, via the 4 holes, |
| 23:32.25 | prpplague | landley: we've had several suggestions for a premade board to put everything on |
| 23:32.26 | landley | Ok, the serial converter is /dev/ttyUSB1. |
| 23:32.31 | prpplague | correct |
| 23:32.49 | landley | It wouldn't fit directly anyway because the serial port's on the wrong side, it would block the power connector. |
| 23:32.50 | prpplague | so you should be able to open up your netcat on that port with the "magic" settings |
| 23:32.57 | prpplague | landley: correct |
| 23:33.24 | prpplague | landley: we always intended it to use a cable |
| 23:33.29 | landley | I did. |
| 23:33.42 | prpplague | landley: got a console? |
| 23:34.10 | landley | Yup. |
| 23:34.14 | landley | Yay console. |
| 23:34.16 | prpplague | hehe |
| 23:35.08 | prpplague | landley: the jtag is really only needed if you are going to be debugging or reflashing the device |
| 23:35.23 | landley | Well, I _had_ a console. It keeps freezing for some reason... |
| 23:36.40 | prpplague | landley: hmm, unplug the power and then remove the jtag connection |
| 23:36.53 | prpplague | landley: power it back on |
| 23:36.56 | landley | Nah, it could easily be my netcat. |
| 23:37.04 | prpplague | landley: ahh ok |
| 23:37.59 | prpplague | landley: i'll take some photo's of the correct placement of the items and post a block diagram tomorrow day |
| 23:38.17 | prpplague | landley: i've got to head home, office closing, i'll be back online in about 15 minutes |
| 23:38.46 | *** join/#edev joe_bleau (n=joe_blea@adsl-69-152-210-234.dsl.fyvlar.swbell.net) |
| 23:59.52 | *** join/#edev redblue (i=star@ppp040.110-253-207.mtl.mt.videotron.ca) |
| 23:59.56 | *** join/#edev dijenerate (n=dijenera@72.51.93.247) |