From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933262AbXCAP4I (ORCPT ); Thu, 1 Mar 2007 10:56:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933286AbXCAP4I (ORCPT ); Thu, 1 Mar 2007 10:56:08 -0500 Received: from de01egw01.freescale.net ([192.88.165.102]:36883 "EHLO de01egw01.freescale.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933262AbXCAP4H (ORCPT ); Thu, 1 Mar 2007 10:56:07 -0500 Message-ID: <45E6F78A.7070603@freescale.com> Date: Thu, 01 Mar 2007 09:55:54 -0600 From: Timur Tabi Organization: Freescale User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: Dan Malek , Torben.Mathiasen@hp.com CC: Segher Boessenkool , Kumar Gala , linux-ppc-embedded , Linux Kernel Mailing List , "H. Peter Anvin" Subject: Re: lanana: Add major/minor entries for PPC QE UART devices References: <45E46976.6060600@freescale.com> <29c13109971547687159078eacdea008@kernel.crashing.org> <45E592DC.9060700@freescale.com> <511cacb7bbe8a65ff72738c84ec9ece4@kernel.crashing.org> <45E5B604.904@freescale.com> <46F6BF70-2922-4E05-8DAB-6B0830B0AB47@embeddedalley.com> <45E5BD6B.1010509@freescale.com> <45E5C128.7020204@freescale.com> <45E5C333.2060100@zytor.com> <45E5D627.6030707@zytor.com> <45E5D84A.5000502@freescale.com> <278AADB6-E175-4177-A728-5357E21697B7@kernel.crashing.org> <45E5DB49.8010205@freescale.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Dan Malek wrote: > People have used more than 4, but we just > allocated the additional /dev entries to cover > them. I know of only one time this has happened. > It's such a custom case that the other device > names didn't matter. Ok guys, I need a consensus here. Are we going to allocate a second block of 4 minor numbers for the QE/CPM UART or not? My driver already has a macro that limits the number of UARTS to 4, and it just uses minor numbers 47 through (47 + UCC_MAX_UART - 1). So my driver can easily be modified to spill into the Altic's range if some custom board needs it. I'll add a second TTY struct to handle the 2nd set of minor numbers if and only if devices-2.6+.txt is updated with that information. -- Timur Tabi Linux Kernel Developer @ Freescale