Re: Sterownik I2C

Article View: pl.comp.os.linux.programowanie

Article #72271

Back to pl.comp.os.linux.programowanie Previous Next

#72271

From: Krzysztof Halasa
Date: Fri, 19 Aug 2011 22:28

23 lines
2037 bytes

"elonica.pl" <bartlomiej.grzeskowiak@gmail.com> writes:

> 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.

Rozwazylbym upgrade do ostatniej. Zreszta tu nie ma wiele do rozwazania,
jesli system nie jest jakos ekstremalnie mocno zmodyfikowany to
oplacalnosc jest oczywista.

> 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 };

Zdaje sie ze lepszym pomyslem jest podanie tego jako parametrow kernela
(modulu), z tym ze jak to dokladnie wyglada to nie pamietam.
-- 
Krzysztof Halasa

Technical Details

Message-ID: <m3d3g1kpcv.fsf@intrepid.localdomain>

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!not-for-mail

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> <3d4b385b-5c2f-4b29-81ca-838a3b575246@k3g2000vbz.googlegroups.com>

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!not-for-mail
From: Krzysztof Halasa <khc@pm.waw.pl>
Newsgroups: pl.comp.os.linux.programowanie
Subject: Re: Sterownik I2C
Date: Sat, 20 Aug 2011 00:28:48 +0200
Organization: NASK - www.nask.pl
Lines: 23
Message-ID: <m3d3g1kpcv.fsf@intrepid.localdomain>
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> <3d4b385b-5c2f-4b29-81ca-838a3b575246@k3g2000vbz.googlegroups.com>
NNTP-Posting-Host: nat.piap.pl
Mime-Version: 1.0
X-Trace: pippin.nask.net.pl 1313785734 15341 195.187.100.13 (19 Aug 2011 20:28:54 GMT)
X-Complaints-To: abuse ATSIGN nask.pl
NNTP-Posting-Date: Fri, 19 Aug 2011 20:28:54 +0000 (UTC)
Cancel-Lock: sha1:PD9deCT9jigvK6PiWtkJYS/eNR8=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Reply to Parent Message