Article View: pl.comp.os.linux.programowanie
Article #72270Re: Sterownik I2C
From: elonica.pl
Date: Thu, 18 Aug 2011 08:47
Date: Thu, 18 Aug 2011 08:47
18 lines
2216 bytes
2216 bytes
Tak, to jest driver adapreta i2c. Wyglada, ze u mnie
rtc_device_register() nie tworzy pliku automatycznie. To jest dosc
stary kernel - 2.6.21.
Ok. Zaczelo dzialac po przeanalizowaniu kolejnych wywolan z
printk(KERN_DEBUG "%s[%u]\n", __FUNCTION__, __LINE__);.
Zeby funkcja probe zaczela szukac kosci RTC musialem w rtc-pcf8563.c
dodac ares kosci (0xa2):
/* Addresses to scan: none
* This chip cannot be reliably autodetected. An empty eeprom
* located at 0x51 will pass the validation routine due to
* the way the registers are implemented.
*/
static unsigned short normal_i2c[] = { 0xa2, I2C_CLIENT_END };
Pozdrawiam
Bartlomiej Grzeskowiak
Technical Details
Message-ID:
<3d4b385b-5c2f-4b29-81ca-838a3b575246@k3g2000vbz.googlegroups.com>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!agh.edu.pl!news.agh.edu.pl!news.onet.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!feeder1.cambriumusenet.nl!feed.tweaknews.nl!postnews.google.com!k3g2000vbz.googlegroups.com!not-for-mailReferences:
<89c17ddd-6492-40d1-906e-792989e1d4f3@e35g2000yqc.googlegroups.com> <m34o2e5k66.fsf@intrepid.localdomain> <67c90105-f34b-45fe-9a9b-2d07725bf899@fq4g2000vbb.googlegroups.com> <m3tyadgmjn.fsf@intrepid.localdomain> <08db7d3a-2544-4ba6-ad05-c74a1dfbfeb7@df3g2000vbb.googlegroups.com> <m3hb5pm3pz.fsf@intrepid.localdomain>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!agh.edu.pl!news.agh.edu.pl!news.onet.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!feeder1.cambriumusenet.nl!feed.tweaknews.nl!postnews.google.com!k3g2000vbz.googlegroups.com!not-for-mail From: "elonica.pl" <bartlomiej.grzeskowiak@gmail.com> Newsgroups: pl.comp.os.linux.programowanie Subject: Re: Sterownik I2C Date: Thu, 18 Aug 2011 01:47:55 -0700 (PDT) Organization: http://groups.google.com Lines: 18 Message-ID: <3d4b385b-5c2f-4b29-81ca-838a3b575246@k3g2000vbz.googlegroups.com> References: <89c17ddd-6492-40d1-906e-792989e1d4f3@e35g2000yqc.googlegroups.com> <m34o2e5k66.fsf@intrepid.localdomain> <67c90105-f34b-45fe-9a9b-2d07725bf899@fq4g2000vbb.googlegroups.com> <m3tyadgmjn.fsf@intrepid.localdomain> <08db7d3a-2544-4ba6-ad05-c74a1dfbfeb7@df3g2000vbb.googlegroups.com> <m3hb5pm3pz.fsf@intrepid.localdomain> NNTP-Posting-Host: 193.101.167.170 Mime-Version: 1.0 X-Trace: posting.google.com 1313657723 31444 127.0.0.1 (18 Aug 2011 08:55:23 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 18 Aug 2011 08:55:23 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: k3g2000vbz.googlegroups.com; posting-host=193.101.167.170; posting-account=8XX-bwoAAAB8TXULBSxONI_rrl5C-PTv User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HUALESNKRC X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110628 Ubuntu/10.04 (lucid) Firefox/3.6.18,gzip(gfe) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit