The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: "Noel (Sourceforge)" <noelb@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-serial@vger.kernel.org
Subject: Re: PROBLEM: Serial error
Date: Tue, 27 May 2008 16:14:09 +0200	[thread overview]
Message-ID: <483C1731.2060408@gmail.com> (raw)
In-Reply-To: <1211895684.1698.10.camel@roswell.ausics.net>

Noel (Sourceforge) napsal(a):
> On Tue, 2008-05-27 at 23:30, Jiri Slaby wrote:
>> Jiri Slaby napsal(a):
>>> On 05/26/2008 11:14 PM, Noel (Sourceforge) wrote:
>>>> serial comms error with smsclient  >2.6.25 , worked fine up until and
>>>> including 2.6.24.7
>> There is >2.6.25. It means post 2.6.26-rc1 inclusively?
>>
> 
> Yes, it broke as of 2.6.25 , I also obtained  .1 through .4 and still
> broken in each, I have not tried  2.6.26-rc1 as I assume the code
> breaking this is still in the tree
> 
> 
> 
>> If you double checked this, trying to CC Alan if he doesn't have a clue.
>> For reference:
>> http://lkml.org/lkml/2008/5/26/260
> 
> Yes, checked.

Ah, this one goes through platform driver (why do you load istallion and 
stallion drivers?).

8250.c driver changes:
Alan Cox (3):
       serial: Coding style
       serial8250: coding style
       8250: enable rate reporting via termios

Will Newton (1):
       8250.c: support specifying DW APB UARTs in device platform_data

Nothing seems intrusive, but whatever changes in the rest of the serial 
might have caused it. Could you bisect it? I think it would be fast.

git-bisect v2.6.25 v2.6.24 -- drivers/char/ drivers/serial/

      reply	other threads:[~2008-05-27 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 21:14 PROBLEM: Serial error Noel   (Sourceforge)
2008-05-26 22:36 ` Jiri Slaby
2008-05-27 13:30   ` Jiri Slaby
2008-05-27 13:33     ` Jiri Slaby
2008-05-27 13:42       ` Noel   (Sourceforge)
2008-05-27 13:41     ` Noel   (Sourceforge)
2008-05-27 14:14       ` Jiri Slaby [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=483C1731.2060408@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=noelb@users.sourceforge.net \
    /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