From: Andrew Morton <akpm@osdl.org>
To: Michael Westermann <michael@dvmwest.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DTR/DSR handshake in kernelspace third traying
Date: Sat, 9 Dec 2006 22:50:14 -0800 [thread overview]
Message-ID: <20061209225014.0888720b.akpm@osdl.org> (raw)
In-Reply-To: <20061207201626.GA10920@dvmwest.dvmwest.de>
> On Thu, 7 Dec 2006 21:16:27 +0100 Michael Westermann <michael@dvmwest.de> wrote:
> Hello,
>
> I've send 2 patches for a DTS/DSR handshaking to the list
>
> http://lkml.org/lkml/2004/5/7/76 and long long time ago 1998
>
> My problem are manufacturers the make printers with
> DTR/DSR Handschaking. POS Printers are very sensible for
> a buffer overrun!
>
> For on or two printers, we can wire a adapter, for 10000...30000
> printers is a software option the better way.
>
> I've write a patch for 2.2 and published it,
> I've write a patch for 2.4 and published it, but i've see there is no
>
> DTR/DSR Handshaking in the kernel 2.6.
>
> I'm a litte bit frusted. Are a few thousands pos-systems not
> enough for upgrading the standard kernel sources?
>
> Have I a really chance to commit a patch for kernel 2.6.
>
I'd say so. Please make sure that such a patch is against the very latest
Linus kernel from ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots.
Also, the more comprehensive the patch's description the better - why it is
needed, what it does, how it works, etc. Your 2004 description was rather
terse.
I seem to recall that the people who understand and work on this code
discussed this issue earlier this year, but I forget the conclusion. Some
archive searching might be useful.
next prev parent reply other threads:[~2006-12-10 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 20:16 DTR/DSR handshake in kernelspace third traying Michael Westermann
2006-12-10 6:50 ` Andrew Morton [this message]
2006-12-10 12:14 ` Russell King
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=20061209225014.0888720b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@dvmwest.de \
/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