| 00:09.58 | *** join/#elinux TimRiker (i=timr@henrypc.rikers.org) |
| 00:10.04 | *** join/#elinux woodgrain (n=mikejone@dsl017-073-218.chi4.dsl.speakeasy.net) |
| 00:10.14 | *** mode/#elinux [+o TimRiker] by ChanServ |
| 00:10.22 | *** part/#elinux TimRiker (i=timr@pdpc/supporter/bronze/TimRiker) |
| 00:22.27 | *** join/#elinux ibot (i=ibot@rikers.org) |
| 00:22.27 | *** topic/#elinux is #elinux Embedded Linux || http://eLinux.org/ || cross compile, uClibc, busybox, tinylogin, handhelds, post-sale linux installs ;-), etc. || free embedded linux training at http://free-electrons.com/news/news.2004-09-28/en || <prpplague> hmm, never had a problem with yahoo mail before |
| 00:28.52 | *** join/#elinux ibot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 00:28.52 | *** topic/#elinux is #elinux Embedded Linux || http://eLinux.org/ || cross compile, uClibc, busybox, tinylogin, handhelds, post-sale linux installs ;-), etc. || free embedded linux training at http://free-electrons.com/news/news.2004-09-28/en || <prpplague> hmm, never had a problem with yahoo mail before |
| 00:28.52 | *** mode/#elinux [+o ibot] by ChanServ |
| 00:32.24 | *** join/#elinux sjhill (n=sjhill@spvl-02-110.dsl.netins.net) |
| 00:56.34 | *** join/#elinux joe_bleau (n=joe_blea@adsl-69-151-119-72.dsl.fyvlar.swbell.net) |
| 01:27.30 | *** join/#elinux Soopaman (n=soopaman@HSE-Montreal-ppp133764.qc.sympatico.ca) |
| 01:41.54 | Genesis | bonne nuit |
| 01:53.58 | *** join/#elinux Soopaman_ (n=soopaman@HSE-Montreal-ppp134197.qc.sympatico.ca) |
| 02:57.44 | *** join/#elinux we0 (n=weo@p5499BDA8.dip0.t-ipconnect.de) |
| 03:29.16 | *** join/#elinux George (i=george@kde/developer/gwright) |
| 04:03.41 | *** join/#elinux Evanrude (n=david@ip68-107-162-212.lu.dl.cox.net) |
| 04:18.29 | *** join/#elinux TimRiker (n=timr@rikers.org) |
| 04:27.19 | *** part/#elinux joe_bleau (n=joe_blea@adsl-69-151-119-72.dsl.fyvlar.swbell.net) |
| 05:08.35 | *** join/#elinux TimRiker (n=timr@rikers.org) |
| 05:10.18 | *** mode/#elinux [+o TimRiker] by ChanServ |
| 05:35.16 | *** join/#elinux Blue_Sky (n=Blue_Sky@pool-151-199-91-120.roa.east.verizon.net) |
| 08:55.30 | *** join/#elinux Lewoco (n=lewoco@h157.sonartech.com.au) |
| 10:42.14 | *** join/#elinux Lewoco (n=lewoco@h157.sonartech.com.au) |
| 12:28.37 | *** join/#elinux Genesis (n=genesis@dev.aimao.org) |
| 12:30.06 | Genesis | bonjour |
| 12:46.16 | *** join/#elinux |nico| (i=nico@212-100-183-29.adsl.easynet.be) |
| 13:13.33 | *** join/#elinux Sgt-Donan (n=Loutre@feu30-1-82-242-59-35.fbx.proxad.net) |
| 14:00.56 | *** join/#elinux chouimat (n=dieu@kde/developer/chouinard) |
| 14:26.24 | *** join/#elinux GPSFan (n=Ken@65.121.49.208) |
| 15:03.54 | *** join/#elinux mindfunk (n=mindfunk@lala.ices.utexas.edu) |
| 15:21.00 | chouimat | morning |
| 15:52.51 | *** join/#elinux MonMotha (n=monmotha@martinbv-3.student.rose-hulman.edu) |
| 15:58.18 | *** join/#elinux vittorio (n=andreas@213.174.253.3) |
| 16:05.34 | *** join/#elinux mindfunk_ (n=mindfunk@lala.ices.utexas.edu) |
| 16:33.38 | *** join/#elinux Blue_Sky (n=Blue_Sky@pool-151-199-91-120.roa.east.verizon.net) |
| 16:36.56 | *** join/#elinux Sgt-Donan (n=Loutre@mto30-1-82-242-53-8.fbx.proxad.net) |
| 16:55.35 | *** join/#elinux Crofton (n=balister@hc6521d1e.dhcp.vt.edu) |
| 17:14.22 | *** join/#elinux prpplague (n=billybob@72.22.152.142) |
| 17:15.59 | *** join/#elinux Soopaman (n=soopaman@HSE-Montreal-ppp134197.qc.sympatico.ca) |
| 17:27.33 | *** mode/#elinux [+o prpplague] by ChanServ |
| 18:24.37 | *** join/#elinux GPSFan (n=Ken@65.121.49.208) |
| 18:28.58 | *** join/#elinux mbuf (n=mbuf@59.92.97.36) |
| 18:49.31 | mbuf | what is the best way to learn a current specification and its driver implementation? |
| 18:50.42 | prpplague | mbuf: pretty much just like you just said, you get the spec, read it, and compare it to the docs and code in the kernel |
| 18:51.34 | mbuf | prpplague, its like, you have a spec, you see a driver implementation, and you already know it works - but you want to understand how it works, where and how control flow occurs etc. |
| 18:52.39 | prpplague | mbuf: i usually install a ton of printf's or printk's |
| 18:52.48 | prpplague | and just experiment |
| 18:54.34 | mbuf | prpplague, but wouldn't that lead to timing mismatches or missed interrupts, especially when dealing with drivers ? |
| 18:55.55 | prpplague | mbuf: possible, but mostly i just place them in areas where decisions are mad |
| 18:55.56 | prpplague | made |
| 18:56.12 | mbuf | i see |
| 19:14.29 | *** join/#elinux runxctry (n=franklin@ppp-71-136-95-115.dsl.sndg02.pacbell.net) |
| 19:15.49 | runxctry | hi everyone! i'm interested in learning how to write embedded linux drivers |
| 19:16.15 | runxctry | i got a book -- writing linux device drivers -- and i'm going to start just writing drivers on a ubuntu desktop |
| 19:16.23 | runxctry | do you think that's a good place to start? |
| 19:19.10 | prpplague | runxctry: yea |
| 19:19.40 | vittorio | runxctry, never wrote a driver, but i think its a good place to start |
| 19:20.09 | runxctry | awesome, thank you for your responses! |
| 19:20.11 | vittorio | or get a board with linux and write drivers for this board |
| 19:20.18 | runxctry | oh yea that's actually the goal |
| 19:20.35 | runxctry | we have a TI board w/ dsp on it |
| 19:20.46 | runxctry | linux is up and going on it already |
| 19:20.47 | Crofton | which ti board? |
| 19:20.49 | runxctry | but no drivers |
| 19:20.50 | prpplague | runxctry: which kit? the OSK? |
| 19:20.52 | runxctry | it's an OMAP |
| 19:20.56 | *** join/#elinux mbuf (n=mbuf@59.92.97.36) |
| 19:20.59 | runxctry | yea i think OSK |
| 19:21.00 | prpplague | runxctry: omap covers alot of chips |
| 19:21.00 | vittorio | which bard? |
| 19:21.01 | file | dear god, there's life in here |
| 19:21.03 | runxctry | haha |
| 19:21.05 | Crofton | 5912? |
| 19:21.07 | prpplague | ~osk |
| 19:21.08 | ibot | somebody said osk was the OMAP5912 Starter Kit, a $295 development board with 32/32, serial, ethernet, usb host/client, CF, jtag, and expansion connectors available from http://www.spectrumdigital.com/cgi/catalog.cgi?show_product=701875 or http://tree.celinuxforum.org/pubwiki/moin.cgi/OSK, or http://www.ti.com/omap5912osk |
| 19:21.08 | runxctry | yes |
| 19:21.10 | runxctry | 5912!! |
| 19:21.15 | runxctry | it's awesome |
| 19:21.23 | Crofton | what driver do you need? |
| 19:21.40 | vittorio | runxctry, do you have a URL? |
| 19:21.53 | runxctry | hmm i'm not really sure yet i'm just assigned to researching and developing the project |
| 19:22.03 | runxctry | i suppose a simple rs232 driver |
| 19:22.06 | vittorio | ah ibot told the URL already |
| 19:22.10 | mbuf | access to FS partitions can be done only from user-space? can another driver write to a filesystem partition from and to kernel-space ? |
| 19:22.11 | Crofton | hmmm |
| 19:22.15 | runxctry | and understanding it is in the realm of learninng already |
| 19:22.21 | Crofton | that should already work |
| 19:22.38 | Crofton | the 2.6 kernel pretty much has support for everything on the osk |
| 19:22.56 | runxctry | actually one of our goals is to boot the OS from the onboard??? flash |
| 19:23.04 | runxctry | but to load our extensions and programs from CF |
| 19:23.30 | runxctry | yea ibot listed all the links i have visited |
| 19:23.58 | runxctry | well the OS is already booting but we want to be able to access the CF automagically, im guessing using symbolic links |
| 19:24.04 | runxctry | but we don't even know how to access it |
| 19:24.09 | runxctry | work in progress |
| 19:24.29 | Crofton | its not hard |
| 19:24.44 | Crofton | I used a microdrive in the cf port |
| 19:24.58 | Crofton | and sym linked thing like /usr to the micrdorve |
| 19:25.39 | runxctry | i see |
| 19:25.58 | runxctry | hmm so the kernel natively supports the CF |
| 19:26.06 | Crofton | it should |
| 19:26.12 | runxctry | got it |
| 19:26.16 | Crofton | you using the one that came with it? |
| 19:26.21 | runxctry | nope |
| 19:26.23 | runxctry | wrote our own |
| 19:26.30 | Crofton | 2.6? |
| 19:26.36 | runxctry | checking... |
| 19:26.44 | Crofton | the 2.6 omap version? |
| 19:27.50 | runxctry | i don't think so |
| 19:28.23 | runxctry | i think my buddies had to make a lot of modifications to get it to run on the processor |
| 19:28.41 | runxctry | they used a suse distro |
| 19:29.01 | runxctry | okay very cool |
| 19:29.11 | runxctry | you guys have been a lot of help for getting me started |
| 19:29.13 | runxctry | i'll be back!! |
| 19:31.23 | Crofton | you need to find to the linux-omap kernel list |
| 19:35.43 | vittorio | afaik the nokia 770 uses the 5912 |
| 19:35.45 | runxctry | hmm haven't found it on searchirc.com |
| 19:36.07 | *** join/#elinux darkschneider (n=gab@213-140-6-96.ip.fastwebnet.it) |
| 19:36.21 | Crofton | standby |
| 19:36.35 | vittorio | i thought the 5912 is only available when order in high volumes? |
| 19:36.46 | Crofton | http://linux.omap.com/mailman/listinfo/linux-omap-open-source |
| 19:37.40 | Crofton | http://oskfordummies.hp.infoseek.co.jp/ |
| 19:37.49 | runxctry | oh not an irc channel got it |
| 19:38.00 | Crofton | you can try #ol |
| 19:38.27 | Crofton | but most of the omap sorts also hang out here |
| 19:38.35 | runxctry | sweet deal! |
| 19:38.44 | runxctry | i've seen the 1st one |
| 19:38.46 | runxctry | but the 2nd one is sweet |
| 19:39.06 | Crofton | what are you going to do with your osk? |
| 19:39.54 | runxctry | run some image recognition software on it |
| 19:40.14 | runxctry | it's already built and running on desktops |
| 19:40.19 | Crofton | ah |
| 19:40.22 | runxctry | but it'd be cool to get a mobile version of it going |
| 19:40.31 | Crofton | yeah |
| 19:45.50 | beeble | sorry very offtopic. but can somebody explain me what a twin bed is? |
| 19:46.14 | beeble | is this a normal one person bed? |
| 19:51.23 | runxctry | yea |
| 19:51.31 | Crofton | hehe |
| 19:51.37 | runxctry | it's like 1 m wide by i dunno |
| 19:51.42 | runxctry | just under 6 feet long |
| 19:52.30 | beeble | oh, thats not so good |
| 19:52.38 | runxctry | yea kind of small actually |
| 19:52.56 | beeble | im 6.5 feet tall ;) |
| 19:53.05 | runxctry | yea you're screwed |
| 19:53.17 | runxctry | a lot of ppl your size get like a nightstand that they put bheind the bed |
| 19:53.21 | runxctry | your feet go on it |
| 19:53.40 | runxctry | or i have what's called an extra-long twin |
| 19:53.45 | runxctry | but it's only longer by like 3 inches |
| 19:54.14 | beeble | ok, so i must cuddle with my colleague and get a double bed |
| 19:55.46 | runxctry | yea my gf & i are two little asian people |
| 19:55.54 | runxctry | but at 6.5 feet, i think that will be more difficult |
| 20:17.25 | *** join/#elinux file[laptop] (n=jcolp@mctnnbsa24w-142167048221.nb.aliant.net) |
| 20:17.25 | *** mode/#elinux [+v file[laptop]] by ChanServ |
| 21:36.34 | woodgrain | How can I find an IRC channel for embedded arm7 ?? |
| 22:35.11 | *** join/#elinux FireEgl (i=Atlantic@Atlantica.US) |
| 22:46.29 | MonMotha | woodgrain: well, if it involves Linux, here is just fine |
| 22:46.37 | MonMotha | even if it doesn't, other embedded type discussion does go on |
| 22:52.14 | woodgrain | MonMotha, no looking for arm7 irc for use w/o OS. |
| 22:54.34 | MonMotha | I'm not aware of any channels dedicated to such a thing, sorry |
| 22:54.51 | MonMotha | though if you have questions, it is possible someone in here could help you. ARM7 is a rather popular platform |
| 23:37.34 | *** join/#elinux Crofton (n=balister@66-207-66-26.black.dmt.ntelos.net) |
| 23:39.11 | woodgrain | Anyone here develop for ARM7 w/o OS? |
| 23:44.27 | *** join/#elinux myopiate (n=me@ivwall.ivolve.com) |