From: Vitaly Bordug <vbordug@ru.mvista.com>
To: "Alexandros Kostopoulos" <akostop@inaccessnetworks.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: uart_cpm scc Rx problem after second open of the device
Date: Mon, 28 Aug 2006 18:50:22 +0400 [thread overview]
Message-ID: <20060828185022.51e98fc4@vitb.ru.mvista.com> (raw)
In-Reply-To: <op.tezypejhnhx3hy@draco>
On Mon, 28 Aug 2006 17:04:16 +0300
"Alexandros Kostopoulos" <akostop@inaccessnetworks.com> wrote:
> I experienced a problem with the cpm_uart scc driver (kernel version
> 2.6.13) while running the driver for a serial port NOT configured as a
> console.
> The problem is as follows:
> The first time the device (/dev/ttyCPM0) is opened, everything works ok.
> The second time, however, the device is opened, receive does not work. The
> device can only transmit, but doesn't receive anything.
>
I'm recalling to fix it a while ago (later than .14 though). There were not just the line below,
but you cant find the respective stuff on the line (linuxppc-embedded) archive/ kernel git.
--
Sincerely,
Vitaly
prev parent reply other threads:[~2006-08-28 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 14:04 uart_cpm scc Rx problem after second open of the device Alexandros Kostopoulos
2006-08-28 14:50 ` Vitaly Bordug [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=20060828185022.51e98fc4@vitb.ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=akostop@inaccessnetworks.com \
--cc=linuxppc-dev@ozlabs.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