From: Roman Kurakin <rik@cronyx.ru>
To: matts@commtech-fastcom.com
Cc: linux-serial@vger.kernel.org
Subject: Re: development of serial driver
Date: Sun, 03 Jul 2005 01:53:25 +0400 [thread overview]
Message-ID: <42C70CD5.1040808@cronyx.ru> (raw)
In-Reply-To: <MFEBKNPNJBEAJEICJEJNAEAGCLAA.matts@commtech-fastcom.com>
Hi,
You may do like Cronyx did. This probably is not the best way in general,
but if for device is enough a generic support and in case the driver is
not a
part of the system (e.q. need to support different kernel branches) this
is I
am sure the best way.
The driver is available from www.cronyx.ru:
http://www.cronyx.ru/software/omega.html
rik
Matt Schulte:
>Wednesday, June 29, 2005 12:02 PM Matt Schulte wrote:
>
>
>>I am a developer for a line of multiport PCI serial cards. I
>>have received
>>enough requests that it is time to make the cards work with the 2.6.x
>>kernels. I see that serial.c has been deprecated and I am wondering if
>>anyone can tell me exactly how the serial is supposed to work in the new
>>kernel?
>>
>>How can I modify the existing stock driver to include my card as well? Is
>>there a CVS version somewhere that I could checkout? Do I send patches
>>somewhere?
>>
>>
>
>I have been painfully digging through the linux kernel mailing list archive
>and I have a pretty good idea of how I can submit patches that I come up
>with to make my driver operate in the new serial driver.
>
>In the past (2.4.x days) I have just hacked the serial.c code to do what I
>needed and then recompiled it as something else.
>
>I would like for someone to explain to me exactly how a guy like me is
>"supposed" to use this new driver. Let's say that I have submitted a patch
>to 8250_pci.c that inserts my cards' device and vendor ids and my cards'
>.initialize and .setup routines (if I need them). Now they can be
>recognized by the driver and will initialize correctly as 16550A type ports.
>Now I need to be able to write a few routines that can configure my card's
>special features. In my hijacked serial.c I just added these routines as
>IOCTL's and life was good. How should I write these routines now?
>
>Many Thanks,
>
>Matt Schulte
>Commtech, Inc.
>http://www.commtech-fastcom.com
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-serial" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2005-07-02 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 17:01 development of serial driver Matt Schulte
2005-07-01 22:06 ` Matt Schulte
2005-07-02 21:53 ` Roman Kurakin [this message]
2005-07-05 16:00 ` development of serial driver (i.e. 8250_pci HOWTO) Matt Schulte
2005-07-05 16:47 ` Roman Kurakin
2005-07-05 17:03 ` Matt Schulte
2005-07-05 17:34 ` Roman Kurakin
2005-07-16 11:06 ` development of serial driver Carl-Daniel Hailfinger
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=42C70CD5.1040808@cronyx.ru \
--to=rik@cronyx.ru \
--cc=linux-serial@vger.kernel.org \
--cc=matts@commtech-fastcom.com \
/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.