Search:

Nur damit der Thread sauber beendet werden kann ;): da wird die Datei noch aus dem lokalen Cache von davfs2 geholt, nicht vom Server.

Was T-Online angeht, kannst Du das zur Zeit vergessen. Mit der Beta-Version des Mediencenters hat es noch funktioniert. Seit der offiziellen Freigabe aber benutzt das Mediencenter Redirects und die...

The OpenWRT wiki page for the WL-HDD still exists. The code there is for WhiteRussian. There's also some source code for Kamikaze, see ticket #1873.

Note that it only supports the WL-HDD, not the...

Ich weiß nur, was im Datenblatt steht. Und nichtflüchtigen Speicher hat der Chip nicht. Das Absinken der Versorgungsspannung unter die 2.1V heißt nicht automatisch, dass die Uhr nicht mehr geht. Es...

Das bedeutet, dass die Versorgungsspannung des RTC Chips mal unterhalb von 2.1V war und der Autor des RTC-Treibers etwas geschlampt hat. Hätte er das Datenblatt zum Uhrenchip nämlich zu Ende gelesen,...

Nein,

Du hast auf der WL-HDD (wie auf normalen PCs auch) eine RTC und eine Systemclock. Die RTC ist ein Stück Hardware und wird üblicherweise mit 'hwclock' gesetzt und gelesen. Die Systemclock ist...

I shouldn't have called this simply rtc.c at all, as the name wrongly implies some generic rtc stuff. I'd recommend rtc-rv5c386a.c which fits the current naming scheme of rtc drivers in the linux...

In my opinion, this isn't needed at all. The reason why I implemented it compatible to the original asus code was just the missing hwclock applet.

That shouldn't be a problem to implement. I assume you can do this yourself ;).



The switch to 24h mode doesn't really destroy the setting. Depending on the current time, it just leads to...

Ricoh RV 5C386A

Ok, here it is. Note that I've already modified the code to the best of my knowledge to comply with your changed function calls.



That might be true. I stopped thinking about whether or not...

That means that the time/date read from the RTC is invalid.



Since it is working with the previous firmware release, this means that the I2C communication to the RTC chip doesn't work.

I've...

That seems to be difficult without an error message. If you followed this thread from where I jumped in, you might have noticed that I don't run Oleg's firmware on my box, so I can't verify this...

Yes, of course a standalone (x)inetd will also work. In case of xinetd, the file /etc/xinetd.d/time (or wherever your xinetd has its configuration file(s)) with the following content should do the...

Theoretically, yes. You need an inetd running which supports the time service. If you don't have inetd on your WL-HDD, you need to recompile busybox with inetd (and the time service) enabled. If you...

Great! Now, after the module is working, could you please try the attached one. It fixes two bugs. Only one of it is relevant for you: because of a bug in the 12h<->24h calculations, the module...

Ok, here is my last attempt for now. This time I have compiled the file using different compiler flags and the asus toolchain instead of the OpenWrt SDK. I'll keep my fingers crossed...


UPDATE:...

Hmm, too bad :( . There's still one attempt left. I have attached a previous version of the module, which doesn't use the kernel supplied interface to the gpio pins, but directly accesses them...

First make sure that you have the correct device entry. It might be that you have the wrong entry from the rtcdrv.o module.

If not, create the correct device node first:

Then a simple
should...

Since I also had some trouble with the proprietary rtcdrv.o module, I simply wrote my own one. If you trust me enough ;), try the attached rtc.o module. I have compiled it for OpenWrt (WhiteRussian...