From: Ingo Molnar <mingo@elte.hu>
To: Mark Kelly <mark@bifferos.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Florian Fainelli <florian@openwrt.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch] x86 CPU detection for RDC
Date: Sun, 16 Aug 2009 19:52:04 +0200 [thread overview]
Message-ID: <20090816175204.GA28553@elte.hu> (raw)
In-Reply-To: <alpine.LNX.2.00.0908160317250.19588@cent.localnet>
* Mark Kelly <mark@bifferos.com> wrote:
> +static void __cpuinit rdc_identify(struct cpuinfo_x86 *c)
> +{
> + u16 vendor, device;
> + u32 customer_id;
> +
> + /* RDC CPU is SoC (system-on-chip), Northbridge is always present. */
> + vendor = read_pci_config_16(0, 0, 0, PCI_VENDOR_ID);
> + device = read_pci_config_16(0, 0, 0, PCI_DEVICE_ID);
> +
> + if (vendor != PCI_VENDOR_ID_RDC || device != PCI_DEVICE_ID_RDC_R6020)
> + return; /* not RDC */
> +
> + /* NB: We could go on and check other devices, e.g. r6040 NIC, but
> + that's probably overkill */
please use the customary (multi-line) comment style:
/*
* Comment .....
* ...... goes here.
*/
specified in Documentation/CodingStyle.
> + strcpy(c->x86_vendor_id, "RDC");
> + c->x86_vendor = X86_VENDOR_RDC;
> +
> + customer_id = read_pci_config(0, 0, 0, 0x90);
> +
> + switch (customer_id) {
> + /* id names are from RDC */
> + case 0x00321000:
> + strcpy(c->x86_model_id, "R3210/R3211");
> + break;
> + case 0x00321001:
> + strcpy(c->x86_model_id, "AMITRISC20000/20010");
> + break;
> + case 0x00321002:
> + strcpy(c->x86_model_id, "R3210X/Edimax");
> + break;
> + case 0x00321003:
> + strcpy(c->x86_model_id, "R3210/Kcodes");
> + break;
> + case 0x00321004: /* tested */
> + strcpy(c->x86_model_id, "S3282/CodeTek");
> + break;
> + case 0x00321007:
> + strcpy(c->x86_model_id, "R8610");
> + break;
> + default:
> + printk(KERN_INFO "Unrecognised Customer ID (0x%x) please "
> + "report to bifferos@yahoo.co.uk\n", customer_id);
I'd rather see them reported to linux-kernel@vger.kernel.org. Also,
please concatenate the string on a single line (and ignore the
checkpatch warning in this case, even if the line is over-long).
Also, please use pr_info() here. Plus, put 'RDC' into the printout
so that people know that the RDC cpu is unknown. (it's not clear
from this printk)
> + /* We'll default to the R321x since that's mentioned
> + elsewhere in the kernel sources */
> + strcpy(c->x86_model_id, "R321x");
> +
> + /* blank the vendor_id, so we get a warning that this
> + is unsupported, your system may be unstable etc...
> + Is there a better way? */
(these multi-line comments too need to be fixed.)
> + strcpy(c->x86_vendor_id, "");
hm, the default should already be an empty string (i.e. \0) - why
does this need to be cleared again?
Ingo
next prev parent reply other threads:[~2009-08-16 17:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 15:46 [patch] x86 CPU detection for RDC Mark Kelly
2009-08-16 15:55 ` Ingo Molnar
2009-08-16 2:20 ` Mark Kelly
2009-08-16 17:52 ` Ingo Molnar [this message]
2009-08-16 3:35 ` Mark Kelly
2009-08-17 17:57 ` H. Peter Anvin
2009-08-17 18:08 ` Ingo Molnar
2009-08-17 18:22 ` H. Peter Anvin
2009-08-17 18:46 ` Andi Kleen
2009-08-17 18:53 ` H. Peter Anvin
2009-08-17 21:31 ` Andi Kleen
2009-08-17 22:00 ` H. Peter Anvin
2009-08-17 7:13 ` [patch, v2] x86: " Mark Kelly
2009-08-18 9:21 ` Florian Fainelli
2009-08-18 10:15 ` Ingo Molnar
2009-08-18 2:56 ` [patch, v3] " Mark Kelly
2009-08-17 18:58 ` [patch] x86 " H. Peter Anvin
2009-08-17 13:44 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090816175204.GA28553@elte.hu \
--to=mingo@elte.hu \
--cc=florian@openwrt.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@bifferos.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox