Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot]  hwclock again
@ 2010-09-02 11:29 JNY
  2010-09-02 11:42 ` Anders Darander
  2010-09-02 12:02 ` Thomas Petazzoni
  0 siblings, 2 replies; 5+ messages in thread
From: JNY @ 2010-09-02 11:29 UTC (permalink / raw)
  To: buildroot


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?
-- 
View this message in context: http://old.nabble.com/hwclock-again-tp29603222p29603222.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Buildroot] hwclock again
  2010-09-02 11:29 [Buildroot] hwclock again JNY
@ 2010-09-02 11:42 ` Anders Darander
  2010-09-02 11:50   ` JNY
  2010-09-02 12:02 ` Thomas Petazzoni
  1 sibling, 1 reply; 5+ messages in thread
From: Anders Darander @ 2010-09-02 11:42 UTC (permalink / raw)
  To: buildroot

Hi,

On Thu, Sep 2, 2010 at 13:29, JNY <jny0@hotmail.com> wrote:
> 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).

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Buildroot] hwclock again
  2010-09-02 11:42 ` Anders Darander
@ 2010-09-02 11:50   ` JNY
  2010-09-02 12:12     ` Anders Darander
  0 siblings, 1 reply; 5+ messages in thread
From: JNY @ 2010-09-02 11:50 UTC (permalink / raw)
  To: buildroot


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?
-- 
View this message in context: http://old.nabble.com/hwclock-again-tp29603222p29603393.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Buildroot] hwclock again
  2010-09-02 11:29 [Buildroot] hwclock again JNY
  2010-09-02 11:42 ` Anders Darander
@ 2010-09-02 12:02 ` Thomas Petazzoni
  1 sibling, 0 replies; 5+ messages in thread
From: Thomas Petazzoni @ 2010-09-02 12:02 UTC (permalink / raw)
  To: buildroot

On Thu, 2 Sep 2010 04:29:07 -0700 (PDT)
JNY <jny0@hotmail.com> 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
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Buildroot] hwclock again
  2010-09-02 11:50   ` JNY
@ 2010-09-02 12:12     ` Anders Darander
  0 siblings, 0 replies; 5+ messages in thread
From: Anders Darander @ 2010-09-02 12:12 UTC (permalink / raw)
  To: buildroot

Hi,

On Thu, Sep 2, 2010 at 13:50, JNY <jny0@hotmail.com> wrote:
>
> 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?

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-09-02 12:12 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-09-02 11:29 [Buildroot] hwclock again JNY
2010-09-02 11:42 ` Anders Darander
2010-09-02 11:50   ` JNY
2010-09-02 12:12     ` Anders Darander
2010-09-02 12:02 ` Thomas Petazzoni

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox