| To: | Andrew Sharp <tigerand@gmail.com> |
|---|---|
| Subject: | Re: [PATCH 2/5] mips: PMC MSP71xx mips common |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Wed, 28 Feb 2007 19:42:51 +0000 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <20070227184555.GA32425@onstor.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <45E465C1.50408@pmc-sierra.com> <20070227184555.GA32425@onstor.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.2.2i |
On Tue, Feb 27, 2007 at 10:46:01AM -0800, Andrew Sharp wrote: > Experience. ~:^) You never know when a little extra room for expansion > might come in handy. For example, let's say next year you release a > quad-core SOC (hint-hint), and a line of eval boards. You would have > room to put them in the file next to your other boards. But just a > suggestion. Since mips_machtype and mips_machgroup are mostly used to identify systems within Linux changing would not be the most terrible thing on earth. There is no requirement for these numbers to be contiguous either. Ralf |
| Previous by Date: | Re: [PATCH 2/5] mips: PMC MSP71xx mips common, Ralf Baechle |
|---|---|
| Next by Date: | Re: [PATCH 2/5] mips: PMC MSP71xx mips common, Ralf Baechle |
| Previous by Thread: | Re: [PATCH 2/5] mips: PMC MSP71xx mips common, Andrew Sharp |
| Next by Thread: | Re: [PATCH 2/5] mips: PMC MSP71xx mips common, Marc St-Jean |
| Indexes: | [Date] [Thread] [Top] [All Lists] |