development of serial driver

development of serial driver

[Matt Schulte]

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?

Does anyone even read this list anymore?

Thank you,

Matt Schulte
Commtech, Inc.
Voice: 316-636-1131
Fax: 316-636-1163
http://www.commtech-fastcom.com

RE: development of serial driver

[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

Re: development of serial driver

[Roman Kurakin]

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

RE: development of serial driver (i.e. 8250_pci HOWTO)

[Matt Schulte]

> Roman Kurikin wrote:
> 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.

Roman, thank you for the suggestion.  While what you have done with your
driver is definitely a way of getting my card installed, I would still like
to see and example or a description of the "correct" way of going about this
with the new serial driver.

Matt Schulte
Commtech, Inc.
http://www.commtech-fastcom.com

Re: development of serial driver (i.e. 8250_pci HOWTO)

[Roman Kurakin]

Hi,

Matt Schulte wrote:

>>Roman Kurikin wrote:
>>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.
>>    
>>
>
>Roman, thank you for the suggestion.  While what you have done with your
>driver is definitely a way of getting my card installed, I would still like
>to see and example or a description of the "correct" way of going about this
>with the new serial driver.
>  
>
I suggest you to compile docbook for kernel. You may read there API 
description.

rik

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

RE: development of serial driver (i.e. 8250_pci HOWTO)

[Matt Schulte]

> Roman Kurikin wrote:
> I suggest you to compile docbook for kernel. You may read there API
> description.
>

I'm afraid I am going to have to plead ignorance.  Exactly what docbook are
you referring to?

Matt Schulte
Commtech, Inc.
http://www.commtech-fastcom.com

Re: development of serial driver (i.e. 8250_pci HOWTO)

[Roman Kurakin]

Matt Schulte wrote:

>>Roman Kurikin wrote:
>>I suggest you to compile docbook for kernel. You may read there API
>>description.
>>
>>    
>>
>
>I'm afraid I am going to have to plead ignorance.  Exactly what docbook are
>you referring to?
>  
>
/usr/src/linux/Documentation/DocBook

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

Re: development of serial driver

[Carl-Daniel Hailfinger]

Matt Schulte wrote:
> 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

Russell King is the maintainer of the 2.6 serial layer. He is the one
to ask about integration.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/