public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@googlemail.com>
To: Thorsten Glaser <tg@debian.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: Linux on Amiga A600, a success story (in progress, with possible patch)
Date: Sun, 29 Jan 2012 09:24:03 +1300	[thread overview]
Message-ID: <4F245963.9070605@gmail.com> (raw)
In-Reply-To: <loom.20120127T184202-114@post.gmane.org>

Hi Thorsten,

Might be the wrong /dev/rtc device - it should be major 254 minor 0

> Actually, it should be /dev/rtc0 (according to my Debian system)
hwclock attempts to open /dev/rtc which is symlinked to rtc0 if udev is 
used.
> and you can find out the correct major number like this:
>
> root@ara5:~ # ll /dev/rtc*
> crw------- 1 root root 254, 0 Dec 26 16:48 /dev/rtc0
> root@ara5:~ # fgrep rtc /proc/devices
> 254 rtc
>
> This is auto-created from devtmpfs (no udev here), FWIW.
With no helpers at all, the devices need to be static files present in 
/dev. The old makedev scripts
(/dev/MAKEDEV) probably need to be overhauled to create the correct 
files to cover this case.
My copy on the Falcon will still create a misc device for RTC,
> My ARAnyM command line contains devtmpfs.mount=1 coupled
> with a few lines in /etc/rc.local:
>
> (test -e /dev/fd || ln -s /proc/self/fd /dev/fd || :)
> (test -e /dev/stdin || ln -s /proc/self/fd/0 /dev/stdin || :)
> (test -e /dev/stdout || ln -s /proc/self/fd/1 /dev/stdout || :)
> (test -e /dev/stderr || ln -s /proc/self/fd/2 /dev/stderr || :)
rc.local hacks are always possible as a last resort :-) Good one, though.

Cheers,

   Michael

  reply	other threads:[~2012-01-28 20:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 18:37 Linux on Amiga A600, a success story (in progress, with possible patch) Patrick Bottelberger
2012-01-23 20:42 ` Geert Uytterhoeven
2012-01-23 23:04   ` Michael Schmitz
2012-01-24  8:41     ` Geert Uytterhoeven
2012-01-24 17:56     ` Patrick Bottelberger
2012-01-24 21:19       ` Geert Uytterhoeven
2012-01-27 17:44     ` Thorsten Glaser
2012-01-28 20:24       ` Michael Schmitz [this message]
2012-01-28 20:43         ` Thorsten Glaser
2012-01-28 20:49           ` Geert Uytterhoeven
2012-01-28 21:01             ` Thorsten Glaser
2012-01-24 17:35   ` Patrick Bottelberger
2012-01-24 21:17     ` Geert Uytterhoeven
2012-01-24 21:49       ` Geert Uytterhoeven
2012-01-25 19:11       ` Patrick Bottelberger
2012-01-26 17:05         ` Patrick Bottelberger
2012-02-07 19:55           ` Patrick Bottelberger
2012-02-07 22:13             ` Thorsten Glaser
2012-02-20 21:38               ` Patrick Bottelberger
2012-02-20 22:09                 ` Andreas Schwab
2012-02-20 22:47                   ` Patrick Bottelberger
2012-02-20 23:02                     ` Andreas Schwab
2012-02-21 10:55                       ` Patrick Bottelberger
2012-01-29 21:59         ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F245963.9070605@gmail.com \
    --to=schmitzmic@googlemail.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox