linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: Regarding the linkstation defconfig
Date: Fri, 24 Apr 2009 22:05:39 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0904242158210.8309@axis700.grange> (raw)
In-Reply-To: <20090424065816.GA15525@ime.usp.br>

On Fri, 24 Apr 2009, Rog=C3=A9rio Brito wrote:

> Hi, Guennadi, Kumar & Co.
>=20
> Guennadi, since you seem to be the one responsible for the
> linkstation/kurobox in the kernel,

That's not howI interpret my role in linkstation development / support.

> I would like to ask you a few things
> that I couldn't quite understand. Please, forgive my ignorance here
> while I ask you some things:
>=20
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>  01. why is anticipatory the default scheduler for linkstations when CFQ
>      is the default scheduler for the rest of the kernel?
>=20
>  02. since kuroboxes/linkstations are meant to store files, is there any
>      reason why they don't have support for large blk devs enabled by
>      default?
>=20
>  03. why is CONFIG_MIGRATION enabled in such low memory devices?
>=20
>  04. why is CONFIG_BLK_DEV_RAM enabled by default?
>=20
>  05. why is SCSI_LOWLEVEL enabled, if no device under that tree is used?
>=20
>  06. idem for CONFIG_NETDEV_10000.
>=20
>  07. idem for CONFIG_WIRELESS.
>=20
>  08. idem for CONFIG_HWMON.
>=20
>  09. idem for CONFIG_CRYPTO_HW.
>=20
>  10. any reason why CONFIG_VIDEO_OUTPUT_CONTROL is configured as a
>      module?
>=20
>  11. any reason why CIFS is not configured with extended attributes,
>      while both ext3 and nfs are?
>=20
>  12. wouldn't it be a good thing to enable CONFIG_PRINTK_TIME?
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

As I already replied to you earlier, I am not particularly interested in=20
fine-tuning and optimisation of defconfigs. IMHO *_defconfigs are only=20
examples of board configuration, that are known to build and work. The=20
rest is up to the user / packager.

> Perhaps similar remarks would apply to the other device that you
> maintain? I forgot its name.
>=20
> Again, please, forgive my ignorance here regarding the questions above.
> I'm really looking for some clarification and to get things in shape
> both on my systems and in the default kernel configuration, in general.

Feel free to submit patches with reasoning to the powerpc ML and=20
respective maintainer as per MAINTAINERS file.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

  reply	other threads:[~2009-04-24 20:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24  6:58 Regarding the linkstation defconfig Rogério Brito
2009-04-24 20:05 ` Guennadi Liakhovetski [this message]
2009-04-24 21:23   ` Rogério Brito
2009-04-24 22:33   ` [PATCH] powerpc: minimizing the configuration of linkstation_defconfig Rogério Brito
2009-04-27 19:29     ` Kumar Gala
2009-04-28  2:27       ` Rogério Brito
2009-04-28 13:16         ` Kumar Gala
2009-04-28 14:48           ` Rogério Brito
2009-04-28 14:54             ` Kumar Gala
2009-04-28 13:03       ` [PATCH 1/2] powerpc: updating the linkstation_defconfig Rogério Brito
2009-04-28 13:32       ` [PATCH 2/2] powerpc: minimizing the configuration of linkstation_defconfig Rogério Brito
2009-05-16 16:04         ` [PATCH] " Rogério Brito
2009-06-11  2:46           ` Kumar Gala
2009-04-28 16:44       ` [PATCH 2/2] " Rogério Brito

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=Pine.LNX.4.64.0904242158210.8309@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rbrito@ime.usp.br \
    /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;
as well as URLs for NNTP newsgroup(s).