From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: m68k 2.6.26-1 vs 2.4.30 comparison
Date: Fri, 15 May 2009 11:57:07 +0200 [thread overview]
Message-ID: <10f740e80905150257p3a1f4c23t5f7a35bad70d5fbe@mail.gmail.com> (raw)
In-Reply-To: <m2octulnkv.fsf@igel.home>
On Fri, May 15, 2009 at 11:31, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Lance Tagliapietra <lancetag@Luminet.net> writes:
>
>> Now, there is a /dev/rtc device of type 10 135. Interestingly, though is that the
>> kernel is looking for an "rtc0" device based on the kernel config. So I'll make
>> that change to the kernel config and re-build and see what I get -- or would it
>> be a better approach to add a /dev/rtc0 c 10 135?
>
> I think you need a c 254 0 device if you use rtc-generic.
Note that the actual number may change, as it's a dynamic major.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-15 9:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 7:28 m68k 2.6.26-1 vs 2.4.30 comparison Lance Tagliapietra
2009-05-03 11:08 ` Geert Uytterhoeven
2009-05-15 2:37 ` Lance Tagliapietra
2009-05-15 9:31 ` Andreas Schwab
2009-05-15 9:57 ` Geert Uytterhoeven [this message]
2009-05-15 17:02 ` Amiga RTC kernel config [was: Re: m68k 2.6.26-1 vs 2.4.30 comparison] Lance Tagliapietra
2009-05-15 20:05 ` Lance Tagliapietra
2009-05-06 6:44 ` m68k 2.6.26-1 vs 2.4.30 comparison Kolbjørn Barmen
2009-05-06 17:45 ` Lance Tagliapietra
2009-05-07 2:37 ` Michael Schmitz
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=10f740e80905150257p3a1f4c23t5f7a35bad70d5fbe@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.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