linux-kernel - Re: [rtc-linux] Re: [PATCH] x86: i2c rtc instead of cmos rtc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090129221925.07f5ab31@i1501.lan.towertech.it>
Date:	Thu, 29 Jan 2009 22:19:25 +0100
From:	Alessandro Zummo <alessandro.zummo@...ertech.it>
To:	Ed Swierk <eswierk@...stanetworks.com>
Cc:	rtc-linux@...glegroups.com, tglx@...utronix.de, mingo@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [rtc-linux] Re: [PATCH] x86: i2c rtc instead of cmos rtc

On Thu, 29 Jan 2009 13:12:49 -0800
Ed Swierk <eswierk@...stanetworks.com> wrote:

> >  I object to options of this kind. It took us a lot of efforts to move
> >  to the new i2c model and to the concept that devices have to be declared
> >  in the board support code. This kind of hack is in the opposite direction.  
> 
> I see. I encountered board support code when I worked with PowerPC
> boards on Linux years ago but I haven't seen this in the x86 arch
> code. Can you point me to an example?

 Under x86 the thing is not well defined, but you can check 

 arch/x86/kernel/olpc.c

 for an example.

 If you just have to load different modules I'd use an initrd
 where you can place all the necessary logic to detect your board
 

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/