Skip to contentSkip to conversation

hwclock again

Buildroot JNY 3 participants 5 messages Sep 2, 2010

lore
Share & tools
lore

JNY

author
#0 lore raw

Hi,

I've enabled
CONFIG_RTC=y
CONFIG_GEN_RTC=y
in linux-2.6.32.9.config and set the environment variable to read this file. After building and installing, I still get '/dev/misc/rtc': No such file or directory when I use hwclock.

Why won't the hwclock work?

Signature · 2 lines
View this message in context: http://old.nabble.com/hwclock-again-tp29603222p29603222.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
#1 lore raw

Hi,

Quoted 2 lines · JNY

After building and installing, I still get '/dev/misc/rtc': No such file or directory when I use hwclock.

Just to check...
Do you have such a device (/dev/misc/rtc) in the target file system?

Regards,
Anders

(I'm resending, as I missed to CC the mailinglist).

author
#2 lore raw

just to check...
Do you have such a device (/dev/misc/rtc) in the target file system?

Regards,
Anders

-------------------

I have two targets target_skeleton, and target_busybox_skeleton (both contained in target/generic), neither of which contain /dev/misc/rtc. However, neither contain ttyS0, and that ends up on the system when it's loaded, and works. What's going on?

Signature · 2 lines
View this message in context: http://old.nabble.com/hwclock-again-tp29603222p29603393.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
#3 lore raw

Hi,

Quoted 7 lines · JNY

just to check...
Do you have such a device (/dev/misc/rtc) in the target file system?

Regards,
Anders

Quoted 6 lines

-------------------

I have two targets target_skeleton, and target_busybox_skeleton (both contained in target/generic), neither of which contain /dev/misc/rtc. However, neither contain ttyS0, and that ends up on the system when it's loaded, and works. ?What's going on?

Well, I meant the target file system being generated, not the actual skeletons... Either loopback mount the generated file system, generate tar:ed file system, or look directly at your target.

You'll also have a file, device_table.txt, that, among other things, specifies device nodes to be generated. You'll most certainly find ttyS0 being generated from this file.

Regards,
Anders

#4 lore raw
In reply to JNY
Quoted 8 lines · On Thu, 2 Sep 2010 04:29:07 -0700 (PDT) JNY <[email protected]> wrote:

I've enabled
CONFIG_RTC=y
CONFIG_GEN_RTC=y
in linux-2.6.32.9.config and set the environment variable to read this file. After building and installing, I still get '/dev/misc/rtc': No such file or directory when I use hwclock.

Why won't the hwclock work?

Because nobody created /dev/misc/rtc. By default, Buildroot uses a static /dev, so you have to manually add the missing device files.

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com