mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Debian GNU/Linux m68k <debian-68k@lists.debian.org>
Subject: Re: [RFC] m68k: Update defconfigs
Date: Thu, 5 Jan 2012 22:42:54 +1100 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1201052212470.6601@nippy.intranet> (raw)
In-Reply-To: <alpine.DEB.2.00.1201042252450.15625@ayla.of.borg>


On Wed, 4 Jan 2012, Geert Uytterhoeven wrote:

> Findings:
>   - CONFIG_BLK_DEV_SWIM is m, while CONFIG_AMIGA_FLOPPY and
>     CONFIG_ATARI_FLOPPY are y.

My defconfig patch used "m" because (if I recall correctly) the SWIM 
driver is experimental code that couldn't be safely loaded on all 
machines.

>   - Amiga and Atari use CONFIG_RTC_CLASS, the others don't.
>     Should we switch everything to CONFIG_RTC_CLASS (and thus drop
>     CONFIG_GEN_RTC)? We do have CONFIG_RTC_DRV_GENERIC now.

This would alter the device major/minor numbers and devtmpfs path, right?

Also I wonder about CONFIG_RTC_HCTOSYS on Macs without a working RTC 
driver. Would enabling CONFIG_RTC_HCTOSYS change present behaviour?

I suppose it might need some testing. Otherwise, I think harmonising this 
across defconfigs (and distro configs) is a good idea.

Finn

      reply	other threads:[~2012-01-05 11:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 22:05 Geert Uytterhoeven
2012-01-05 11:42 ` Finn Thain [this message]

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=alpine.LNX.2.00.1201052212470.6601@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=debian-68k@lists.debian.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.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

all inboxes | Powered by JetHome®