On Wed, Oct 31, 2012 at 4:55 PM, Matt Schulte <matts@xxxxxxxxxxxxxxxxxxxx> wrote: > On Mon, Oct 29, 2012 at 3:04 PM, Matt Schulte > <matts@xxxxxxxxxxxxxxxxxxxx> wrote: >> On Tue, Oct 23, 2012 at 1:38 PM, Greg KH <greg@xxxxxxxxx> wrote: >>> On Tue, Oct 23, 2012 at 11:31:41AM -0500, Matt Schulte wrote: >>>> On Tue, Oct 23, 2012 at 11:27 AM, Matt Schulte >>>> <matts@xxxxxxxxxxxxxxxxxxxx> wrote: >>>> > On Fri, Oct 19, 2012 at 4:21 PM, Theodore Ts'o <tytso@xxxxxxx> wrote: >>>> >> Alan's advice to get your card working as a basic serial card is very >>>> >> good one. Get basic functionality working, and then you can add the >>>> >> support for the extra bits later.... >>>> > >>>> > I can see the logic in getting it working as a basic serial card >>>> > first. I think at minimum I would still need to implement the extra >>>> > divisor calculations to get accurate bit rates. >>>> > >>>> > So when it works as a basic serial card, I assume you would want me to >>>> > use the default PCI IDs to keep it more generic. Then would I add my >>>> > own PCI IDs and refer them back to the generic port? Hello, the next question that I have is how to handle the interrupts on this UART. It has a more complex interrupt scheme than a traditional 8250 UART. There is a global ISR register that tells you which port had the interrupt and then there is another set of registers that hold the actual interrupts. In this situation where this UART needs extra code for the handling of its interrupt, where is the best place to add this special interrupt handler? Directly to the 8250.c default handler or somewhere else? Thank you, Matt Schulte -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
