| 00:43.25 | *** join/#openmoko chihchun (~chihchun@n201.enc.hlc.edu.tw) |
| 00:53.44 | *** join/#openmoko amarsh04 (~amarsh04@2001:44b8:61::17) |
| 01:32.35 | *** join/#openmoko DieMumie1 (~DieMumiee@p3E9C28D6.dip.t-dialin.net) |
| 04:28.30 | *** join/#openmoko xarragon (~xarragon@67.217.170.35) |
| 04:52.36 | *** join/#openmoko snkt (~snkt@114.143.164.169) |
| 04:53.18 | *** join/#openmoko snkt (~snkt@114.143.164.169) |
| 05:13.13 | *** join/#openmoko DocScrutinizer (~halley@openmoko/engineers/joerg) |
| 06:34.16 | *** join/#openmoko CcSsNET (~CcSsNET@c-98-216-138-179.hsd1.ma.comcast.net) |
| 07:11.02 | *** join/#openmoko ttyS3 (~o@gateway/tor-sasl/omlib) |
| 07:54.10 | snkt | i m working on ARM board ...... I want to integrate external eeprom AT24C04C ... through userspace.... I detected SDA, SCL port with no external peripherals.... so I have to use that slot .... can anyone help... |
| 08:07.44 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.edu) |
| 08:24.43 | *** join/#openmoko jluis (~jluis@gw-guest.ac.upc.edu) |
| 08:47.34 | *** join/#openmoko Martix (~martix@cst-prg-168-3.cust.vodafone.cz) |
| 08:57.11 | *** join/#openmoko jluis (~jluis@gw-guest.ac.upc.es) |
| 08:59.53 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.edu) |
| 09:03.00 | PaulFertser | snkt: can you rephrase your question? |
| 09:03.21 | PaulFertser | snkt: why do you want to use that EEPROM without a kernel driver? |
| 09:03.58 | *** join/#openmoko ThibG (~ThibG@81-64-18-234.rev.numericable.fr) |
| 09:09.50 | snkt | PaulFertser, I have a support in kernel.... i have to just communicate eeprom through userspace... |
| 09:11.06 | PaulFertser | snkt: why do you have to? How the kernel driver (that's there since like forever ;) doesn't suffice? |
| 09:12.14 | snkt | PaulFertser, I want write my own code on that eeprom.... |
| 09:13.48 | PaulFertser | snkt: isn't the sysfs interface provided by the driver good enough? |
| 09:14.41 | snkt | PaulFertser, my I2c slot is empty..... no externel peripherals are connected..... |
| 09:16.01 | PaulFertser | snkt: what do you mean? Do you have an eeprom connected or not? If yes, then what's the issue, if not, then why's the question? ;) |
| 09:16.55 | snkt | PaulFertser, I want solder externally that chip .... |
| 09:18.27 | PaulFertser | snkt: sounds good so far. |
| 09:20.43 | snkt | PaulFertser, please help me after I solder that chip ..... how can I access that chip.... |
| 09:21.21 | PaulFertser | snkt: what makes you think there will be any problems with using the kernel driver and accessing the chip through sysfs interface? |
| 09:22.03 | snkt | PaulFertser, I m newbee to it..... |
| 09:22.15 | *** join/#openmoko jluis (~jluis@gw-guest.ac.upc.edu) |
| 09:23.23 | snkt | PaulFertser, I have worked on I2C protocol on ARM9 and Atmega128 ..... but that was hard coded assembly programming..... I m newbei to access I2C through userspace.... |
| 09:24.05 | PaulFertser | snkt: i do not understand _at all_ why do you want to access i2c from userspace. |
| 09:24.18 | PaulFertser | snkt: because there's already an _in-kernel_ driver for your device. |
| 09:25.07 | snkt | PaulFertser, ok.... hw can I write ,store and read my code on that eeprom...... |
| 09:29.04 | PaulFertser | snkt: the driver will create the file "eeprom" in the sysfs hierarchy. |
| 09:35.34 | *** join/#openmoko Orias_Korva (~atilla@94-227-83-221.access.telenet.be) |
| 09:55.18 | snkt | PaulFertser, yeah... what is I2C address...... I know EEPROM has Slave address as mention in the datasheet.... |
| 09:55.53 | *** join/#openmoko batchy (~batchy@81-64-251-59.rev.numericable.fr) |
| 10:02.45 | *** join/#openmoko Martix (~martix@cst-prg-10-5.cust.vodafone.cz) |
| 10:16.49 | *** join/#openmoko jluis (~jluis@gw-guest.ac.upc.es) |
| 10:17.39 | *** join/#openmoko kirun (~kirun@78-86-154-194.zone2.bethere.co.uk) |
| 10:21.07 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.es) |
| 10:49.22 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.es) |
| 11:09.13 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.es) |
| 11:09.47 | *** join/#openmoko playya (~playya@93.216.225.54) |
| 11:09.48 | *** join/#openmoko playya (~playya@unaffiliated/playya) |
| 11:11.26 | *** join/#openmoko playya (~playya@93.216.225.54) |
| 11:11.27 | *** join/#openmoko playya (~playya@unaffiliated/playya) |
| 11:16.35 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.es) |
| 11:21.44 | *** join/#openmoko amarsh04 (~amarsh04@2001:44b8:61::17) |
| 11:22.39 | *** join/#openmoko amarsh04 (~amarsh04@2001:44b8:61::17) |
| 11:25.23 | *** join/#openmoko Sup3rkiddo (~sudharsh@117.193.173.224) |
| 11:25.33 | *** join/#openmoko Sup3rkiddo (~sudharsh@unaffiliated/sudharsh) |
| 11:36.40 | *** join/#openmoko dos1 (~dos@unaffiliated/dos1) |
| 12:08.30 | *** join/#openmoko Martix (~martix@cst-prg-81-7.cust.vodafone.cz) |
| 12:27.45 | *** join/#openmoko ndnihil (~nihil@adsl-76-236-151-157.dsl.stlsmo.sbcglobal.net) |
| 12:27.45 | *** join/#openmoko ndnihil (~nihil@unaffiliated/ndnihil) |
| 12:38.12 | *** join/#openmoko Openfree` (~Openfreer@124.78.72.45) |
| 13:36.17 | *** join/#openmoko dos1 (~dos@unaffiliated/dos1) |
| 13:44.23 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.edu) |
| 13:50.49 | *** join/#openmoko jluis (~jluis@gw-guest.ac.upc.edu) |
| 13:53.46 | *** join/#openmoko Martix (~martix@cst-prg-52-8.cust.vodafone.cz) |
| 14:03.23 | DocScrutinizer | hah |
| 14:06.53 | *** join/#openmoko tjikkun (~tjikkun@amsn/developer/tjikkun) |
| 14:08.12 | DocScrutinizer | snkt: I bet PaulFertser can tell you what to add to config of kernel (or which module to modprobe in which way) so you get the according /sys/*/* nodes to access your eeprom from userland |
| 14:09.47 | DocScrutinizer | the docs/src of that module will provide the detailed info about (how to use) the sys API for you |
| 14:10.36 | *** join/#openmoko jluis (~jluis@95.214.77.144) |
| 14:14.23 | DocScrutinizer | of course there's also the possibility to do "low level access" to I2C bus directly, from userland (only if the module for handling your EEPROM is *not* loaded as otherwise that module will block direct I2C access) - see i2cget i2cset i2cdump cmdline tools |
| 14:16.19 | DocScrutinizer | I do NOT recommend to use i2ctools when there's a way mire convenient kernel driver aka module to access the EEPROM on a more abstract level - which is what PaulFertser suggested |
| 14:16.22 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.es) |
| 14:16.35 | DocScrutinizer | s/mire/more/ |
| 14:17.14 | DocScrutinizer | PaulFertser: hi! :-D |
| 14:18.26 | DocScrutinizer | snkt: btw, what "ARM board" of yours are we talking bout here? |
| 14:21.26 | snkt | DocScrutinizer, Pollux-ARM |
| 14:27.27 | *** join/#openmoko erwt (~rahul@114.143.164.169) |
| 14:27.41 | erwt | hello |
| 15:33.18 | *** join/#openmoko rah (rah@myrtle.6gnip.net) |
| 16:42.32 | *** join/#openmoko ezekiel (~ezekiel@h-67-100-144-50.nycmny83.static.covad.net) |
| 16:46.00 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.edu) |
| 17:16.36 | *** join/#openmoko pespin (~pespin@gw-guest.ac.upc.edu) |
| 17:47.42 | *** join/#openmoko pespin (~pespin@cisne-cn08.upc.es) |
| 17:48.59 | *** join/#openmoko methril (~methril@189.27.128.79.dynamic.adsl.gvt.net.br) |
| 18:03.49 | *** join/#openmoko aloril (~aloril@dsl-tkubrasgw3-fe7ef900-153.dhcp.inet.fi) |
| 19:14.39 | *** join/#openmoko kirun (~kirun@78-86-154-194.zone2.bethere.co.uk) |
| 19:19.15 | *** join/#openmoko PBeck (~PBeck@unixboard/users/pbeck) |
| 19:20.33 | PBeck | hi |
| 19:57.45 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 19:58.14 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 20:00.44 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 20:01.44 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 20:02.15 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 20:02.44 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 20:03.44 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 20:04.14 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 20:05.14 | *** join/#openmoko hal14450 (~hal@definitely.playingwithoutafulldeck.com) |
| 21:17.16 | ndnihil | phone:~# uptime 16:48:33 up 573 days, 18:26, 1 user, load average: 0.00, 0.07, 0.08 |
| 21:17.24 | ndnihil | ^my freerunner :) |
| 21:34.16 | PBeck | ndnihil: nice uptime - my n900 is not so good ;) i think 2 - 4 weeks is the average |
| 21:36.58 | ndnihil | wish my android phone was that stable |
| 21:37.16 | ndnihil | dont get me wrong, I like it, and it's better than most of the other stuff out there |
| 21:37.32 | ndnihil | but it's no moko for sure |
| 21:44.03 | PBeck | ndnihil: the problem with n900 is often that the sound not works (dont know why) - that means no musicplayer works and no - VERY IMPORTANT - alarm works -.- |
| 21:51.15 | ndnihil | hrm, can you test for it and reload the kernel modules associated with it? |
| 22:00.19 | PBeck | ndnihil: yes i think so, but the problem is not so often - so i only test before i go top sleep if the soundoutput works |
| 22:00.42 | PBeck | at home i have extra alarm it's only important, when i am not at home :) |
| 22:10.32 | ndnihil | anything interesting in the logs? |
| 22:12.53 | PBeck | ndnihil: i have not investigated the problem - it was two times in the last two years and normally i have no laptop or connection ;) |
| 22:54.10 | *** join/#openmoko khorben__ (~khorben@mx.defora.org) |
| 22:54.43 | *** join/#openmoko Fox_Muldr (quakeman@frnk-5f747cea.pool.mediaWays.net) |
| 23:17.38 | *** join/#openmoko Amorphous (jan@unaffiliated/amorphous) |
| 23:28.24 | *** join/#openmoko doc|home (~doc@S01060026f319ba77.vc.shawcable.net) |
| 23:28.25 | *** join/#openmoko doc|home (~doc@gentoo/contributor/doc-007) |
| 23:47.10 | *** join/#openmoko ulrichard_ (~richi@194-80.2-85.cust.bluewin.ch) |
| 23:52.47 | *** join/#openmoko mjr (mjr@nblzone-241-33.nblnetworks.fi) |