LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Jason Wessel <jason.wessel@windriver.com>,
	kgdb-bugreport@lists.sourceforge.net, Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Kgdb-bugreport] [PATCH 4/5] KGDB-8250: refactor configuration
Date: Fri, 01 Feb 2008 22:10:49 +0100	[thread overview]
Message-ID: <47A38AD9.1060305@web.de> (raw)
In-Reply-To: <47A325BC.6030305@ru.mvista.com>

Sergei Shtylyov wrote:
> Hello.
> 
> Jan Kiszka wrote:
> 
>> Sorry, previous version was missing some __init[data] attributes which
>> were dropped in an intermediate stage. Here comes an updated patch:
> 
>> <---snip--->
> 
>> This major refactoring of the quite complex kgdb8250 configuration does
>> the following:
> 
>>  - ensures that static configurations according to SERIAL_PORT_DFNS are
>>    always loaded first
>>  - tries to pull more accurate configuration via serial8250_get_port_def
>>    if simple-config is used
>>  - detects empty/invalid simple-configs
>>  - enforces KGDB_PORT_NUM <= SERIAL_8250_NR_UARTS at kconfig level
>>  - removes kgdb8250_add_port and its hook in serial_core (calling
>>    serial8250_get_port_def in demand should provide us the same
>>    information)
> 
>    You left powerpc-lite.patch broken with this change as it has
> multiple calls to kgdb8250_add_port()...

I see. But I wonder if there ever was a real need for these hooks (in
2.4 times?): If I look at bamboo_early_serial_map() e.g., I find it
calling into early_serial_setup() which fills serial8250_ports[] - and
that content is now retrieved via serial8250_get_port_def() when we
parse the runtime or build-time provided parameters (port number &
baudrate).

> 
>> Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
> 
>> Index: b/drivers/serial/serial_core.c
>> ===================================================================
>> --- a/drivers/serial/serial_core.c
>> +++ b/drivers/serial/serial_core.c
> [...]
>> @@ -2370,12 +2369,6 @@ int uart_add_one_port(struct uart_driver
>>       */
>>      port->flags &= ~UPF_DEAD;
>>  
>> -#if defined(CONFIG_KGDB_8250)
>> -    /* Add any 8250-like ports we find later. */
>> -    if (port->type <= PORT_MAX_8250)
>> -        kgdb8250_add_port(port->line, port);
>> -#endif
>> -
> 
>    I'm afraid this wasn't correct from the very start since this can add
> ports with .iotype that 8250_kgdb.c does not support. So, nothing to
> regret here...

I think a lot of cruft piled up in the kgdb patches over their long life. :)

Thanks for your feedback!

Jan

  reply	other threads:[~2008-02-01 21:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 23:46 Jan Kiszka
2008-01-30  0:31 ` Jan Kiszka
2008-02-01 13:59   ` [Kgdb-bugreport] " Sergei Shtylyov
2008-02-01 21:10     ` Jan Kiszka [this message]
2008-02-06 13:16       ` Sergei Shtylyov
2008-02-06 17:52         ` Jan Kiszka

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=47A38AD9.1060305@web.de \
    --to=jan.kiszka@web.de \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sshtylyov@ru.mvista.com \
    --subject='Re: [Kgdb-bugreport] [PATCH 4/5] KGDB-8250: refactor configuration' \
    /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

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).