From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: New serial card development Date: Tue, 23 Oct 2012 11:38:59 -0700 Message-ID: <20121023183859.GA3317@kroah.com> References: <5074703E.408@commtech-fastcom.com> <20121014093704.GA6207@thunk.org> <20121016002608.64b33de5@pyramind.ukuu.org.uk> <20121016023226.GA17446@thunk.org> <20121019212158.GB4721@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:49652 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933251Ab2JWSpr (ORCPT ); Tue, 23 Oct 2012 14:45:47 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-serial-owner@vger.kernel.org List-Id: linux-serial@vger.kernel.org To: Matt Schulte Cc: Theodore Ts'o , Alan Cox , linux-serial@vger.kernel.org On Tue, Oct 23, 2012 at 11:31:41AM -0500, Matt Schulte wrote: > On Tue, Oct 23, 2012 at 11:27 AM, Matt Schulte > wrote: > > On Fri, Oct 19, 2012 at 4:21 PM, Theodore Ts'o 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? > > > > As more of a procedural question, when I go to make the patch(es) to > submit which, kernel repo do I start with? Do I start with Greg KH's > tty repo and then generate the patches and submit them here? That would be a great place to work off of, use the tty-next branch please. thanks, greg k-h