Dear Alan, The Application we are planning should not require to rebuild the kernel. So, I have found something like /dev/port through which I can access any port i need. I understand this would be a best interface which will does not require any patch and I will have the complete register values I need. Quite a GOOD one. Thanks for all your help. You can see the attached souce code I am planning to use. Regards, Mukund Jampala > -----Original Message----- > From: Alan Cox [mailto:[email protected]] > Sent: Wednesday, December 21, 2005 5:31 AM > To: Mukund JB. > Cc: Dave Jones; [email protected] > Subject: PATCH: day of week (RE: Kernel interrupts disable at > user level > -RIGHT/ WRONG - Help) > > > On Maw, 2005-12-20 at 14:32 +0530, Mukund JB. wrote: > > > > I tried the /dev/rtc but I don't get it there. > > > > > > Use /dev/nvram instead. > > > > > > Dave > > > > /dev/nvram does not give the cpomplete CMOS details. A part > of RTC & date, tine and other info will be missing. > > > What Dave should have said is use /dev/nvram as well. > > >From /dev/rtc you get registers 0-9 except as you said 6 > >From /dev/nvram you get A+ > > The lack of day of week is odd but fixable. The struct tm > already has a > field for tm_wday (day of week) so we can fill it in. Whether it is > valid is another question. > > What do people thing about this ? > > Signed-off-by: Alan Cox <[email protected]> > > --- drivers/char/rtc.c~ 2005-12-20 23:40:34.912559808 +0000 > +++ drivers/char/rtc.c 2005-12-20 23:51:16.428034632 +0000 > @@ -46,10 +46,10 @@ > * 1.11a Daniele Bellucci: Audit > create_proc_read_entry in rtc_init > * 1.12 Venkatesh Pallipadi: Hooks for emulating rtc on > HPET base-timer > * CONFIG_HPET_EMULATE_RTC > - * > + * 1.12ac Alan Cox: Allow read access to the day of week register > */ > > -#define RTC_VERSION "1.12" > +#define RTC_VERSION "1.12ac" > > #define RTC_IO_EXTENT 0x8 > > @@ -1250,9 +1250,9 @@ > > /* > * Only the values that we read from the RTC are set. We leave > - * tm_wday, tm_yday and tm_isdst untouched. Even though the > - * RTC has RTC_DAY_OF_WEEK, we ignore it, as it is only updated > - * by the RTC when initially set to a non-zero value. > + * tm_wday, tm_yday and tm_isdst untouched. Note that while the > + * RTC has RTC_DAY_OF_WEEK, we should usually ignore > it, as it is > + * only updated by the RTC when initially set to a > non-zero value. > */ > spin_lock_irq(&rtc_lock); > rtc_tm->tm_sec = CMOS_READ(RTC_SECONDS); > @@ -1261,6 +1261,9 @@ > rtc_tm->tm_mday = CMOS_READ(RTC_DAY_OF_MONTH); > rtc_tm->tm_mon = CMOS_READ(RTC_MONTH); > rtc_tm->tm_year = CMOS_READ(RTC_YEAR); > + /* Only set from 2.6.16 onwards */ > + rtc_tm->tm_wday = CMOS_READ(RTC_DAY_OF_WEEK); > + > #ifdef CONFIG_MACH_DECSTATION > real_year = CMOS_READ(RTC_DEC_YEAR); > #endif > @@ -1275,6 +1278,7 @@ > BCD_TO_BIN(rtc_tm->tm_mday); > BCD_TO_BIN(rtc_tm->tm_mon); > BCD_TO_BIN(rtc_tm->tm_year); > + BCD_TO_BIN(rtc_tm->tm_wday); > } > > #ifdef CONFIG_MACH_DECSTATION > >
Attachment:
CMOS.C
Description: CMOS.C
- Prev by Date: Un aligned addresses
- Next by Date: Re: ETA for Areca RAID driver (arcmsr) in mainline?
- Previous by thread: Un aligned addresses
- Next by thread: IDE subsytem
- Index(es):
 |