Hi steven, still thanks, hopefully i am near to have i2c working.
config seems exactly like your. I found a possible issue: kernel seems to need exactly as you said, a device named "i2c-0". But uClinux romfs creation seems to fail generating the device into romfs.img: /dev # ls @i2c-0,c,89,0 mtdblock1 ptyp8 rtc0 ttyp5 console mtdblock2 ptyp9 tty ttyp6 cua0 mtdblock3 ptypa tty0 ttyp7 cua1 null ptypb tty1 ttyp8 flash ppp ptypc tty2 ttyp9 ipsec ptyp0 ptypd tty3 ttypa kmem ptyp1 ptype ttyS0 ttypb mem ptyp2 ptypf ttyS1 ttypc mtd0 ptyp3 ram0 ttyp0 ttypd mtd1 ptyp4 ram1 ttyp1 ttype mtd2 ptyp5 ram2 ttyp2 ttypf mtd3 ptyp6 ram3 ttyp3 urandom mtdblock0 ptyp7 random ttyp4 zero /dev # Device name is with "@" before the name also locally in the PC, looking the generated binary romfs.img. Strange thing is that also other vendors use that name (take Simtec/EB675001DIP/Makefile) and i am assuming thay have it working. regards angelo On 24/08/2011 10:56, Viet Nguyen wrote: > Hi Angelo, > > On Wed, Aug 24, 2011 at 2:42 PM, Angelo Dureghello <angel...@gmail.com> wrote: >> On the other hand, i enabled i2c, bus, and dallas 1307 support. How should i >> try that rtc work ? Actually i try to set a "date" and reboot. > > What is your kernel configuration of RTC? > This is mine: > CONFIG_RTC_LIB=y > CONFIG_RTC_CLASS=y > CONFIG_RTC_HCTOSYS=y > CONFIG_RTC_HCTOSYS_DEVICE="rtc0" > > CONFIG_RTC_INTF_PROC=y > CONFIG_RTC_INTF_DEV=y > CONFIG_RTC_DRV_DS1307=y > > By the way, to test in u-boot (2011-06), I just need to define > CONFIG_RTC_DS1338 > CONFIG_CMD_DATE > > Regards, _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
