linux-kernel - Re: [PATCH] generic RTC support for PPC

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]

Date:	Tue, 30 Jan 2007 11:55:46 -0800
From:	David Brownell <david-b@...bell.net>
To:	Kim Phillips <kim.phillips@...escale.com>
Cc:	Olof Johansson <olof@...om.net>, galak@...nel.crashing.org,
	trini@...nel.crashing.org, linuxppc-dev@...abs.org,
	paulus@...ba.org, Scott Wood <scottwood@...escale.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] generic RTC support for PPC

On Tuesday 30 January 2007 11:25 am, Kim Phillips wrote:
> 
> For the MDS boards, which use the ds1374, I'd rather fix the problem properly
> and add a ds1374 driver to the RTC class.  While Scott Wood (cc'd) has already
> done the port, I believe his patches are pending some patches by David Brownell.  

I can't imagine what such patches would be, unless maybe you're referring to
I2C framework updates that make it follow the driver model and support platform
specific data, like an RTC alarm's IRQ number?  Those will take some time.

Just submit a normal I2C driver for that RTC, and any IRQ capability can be
added later.  (Or as a board-specific patch, which seems to be the normal
solution for I2C, though they won't go upstream.)

- Dave

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