Hi Dave, thanks for the reply. Some more questions/comments inline.
David Brownell wrote:
On Monday 15 December 2008, BJ Opp wrote:
All,
I'm currently working on adding a driver for an RTC into our kernel.
The chip I'm working with is the Dallas Semiconductor DS1340 and I've
seen drivers for the ds1337 and ds1338 so they're of the same flavor.
And drivers/rtc/rtc-ds1307.c supports the ds1340, so you
shouldn't need to do much more than use that (in any
reasonably modern kernel).
There's the snag, I guess I'm not fulfilling the 'reasonably modern
kernel' aspect of that because I don't even have the 'rtc' directory in
my kernel. I'm running the 2.6.10 montavista kernel with patchlevel
pro-1721.
I could always just not select Davinci-rtc
from Kconfig
You should only do that on a dm6446evm board in any
case; and one running an old kernel, for that matter.
Though you should have recent firmware (with proprer
reporting of the AM/PM flag) and an updated version of
that driver ...
I'm not running a dm6446evm board, but my custom hardware doesn't have
the msp430 on it so AFAI understood I certainly don't want this kernel
option selected.
and use my own driver and create a device node that way but
if there is a better way I'd like to do it that way instead.
The RTC framework makes most of this stuff painless.
In the current 2.6.28-rc code there are around sixty
drivers (maybe a few are queued in -mm), and when you
use it with udev (or mdev/busybox) you'll get the
right /dev/rtcX nodes created automatically.
... yeah, you may need some of the video or DSP stuff
that's not all running there yet. From the patches
I've seen running around, it seems that objection won't
hold for too much longer.
Not quite sure I follow you here.
- Dave
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
