About :: TODO :: Blog :: RSS :: Old blog :: Projects :: GIT :: Gallery :: Notes

Fri, 28 Sep 2007

Stupidity.

I was asked at work to extend linux 2.6 RTC driver to support read/write operations, so that they would read non-volatile memory (we use DS 1307) of the clock chip. Manager said 'do it like I did in 2.4', after I completed the task, it was shown tht it is wrong approach (there was a cmd-like interface).
After I added sysfs interface for that, management decided that it is not enough, since they have a script, which reads/writes a byte with offset, and sysfs does not support seek.
Existing Linux RTC subsystem does not allow to have read/write operations from RTC device, actually read is supported, but only 4 bytes, which is not enough. So I extended Linux 2.6 RTC driver to be able to read and write via RTC device any amount of data with having backward compatibility with drivers, which read only 4 bytes (only one in kernel tree).
I added needed functionality (testing machine is in the next room, so I need to move there each time I need to test a new kernel), but then hardware where I needed to show result was found to be broken (RTC can not be initialized, although present), so right now I'm trying to determine what the heck is with this hardware...
Crap, I have completely no time for anything other.

/devel/other :: Link / Comments (0)

Comments are closed for this story.