From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] My GT-64260 enhancements
Date: Sun, 17 Mar 02 12:10:43 PST [thread overview]
Message-ID: <0203172010.AA01807@ivan.Harhan.ORG> (raw)
Dan Malek <dan@embeddededge.com> wrote:
> So, I don't see the problem. A default is specified and you can change it,
> just like lots of other configurations.
The problem is that there is a
define_int CONFIG_SERIAL_CONSOLE_BAUD 115200
line in arch/ppc/config.in for "$CONFIG_EV64260" = "y" but not for any other
almost-non-embedded-standard-computer 6xx/7xx/74xx board, which is
discriminatory and undemocratic.
Having "$CONFIG_GT64260" = "y" imply support for CONFIG_SERIAL_TEXT_DEBUG is
also discriminatory and undemocratic. Should we also imply the same then for
"$CONFIG_CPC700" = "y" -o "$CONFIG_CPC710" = "y" -o "$CONFIG_UNINORTH" = "y",
etc?
I mean I don't mind if defaults are changed globally, it's just the
discriminatory treatment of GT-64260 that I violently object to. Oh, and having
a separate BK tree and mailing list for it too isn't something I'm fond of.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev reply other threads:[~2002-03-17 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 18:16 [PATCH] My GT-64260 enhancements Michael Sokolov
2002-03-17 18:42 ` Dan Malek
2002-03-17 20:10 ` Michael Sokolov [this message]
2002-03-18 14:54 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 0:46 Michael Sokolov
2002-03-19 22:55 ` Mark A. Greer
2002-03-15 6:11 Michael Sokolov
2002-03-15 17:04 ` Tom Rini
2002-03-16 8:21 ` Michael Sokolov
2002-03-16 15:15 ` Tom Rini
2002-03-17 7:03 ` Michael Sokolov
2002-03-17 17:51 ` Dan Malek
2002-03-17 20:24 ` David Monro
2002-03-18 15:00 ` Tom Rini
2002-03-18 15:53 ` [Linux-galileo] " Mark A. Greer
2002-03-18 18:48 ` Tom Rini
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=0203172010.AA01807@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linux-galileo@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.