Hi John:
I will try mutt or mail when i want to send next patch. Most different of
ip100a.c
and sundance.c are almost same only fix some bugs. The different of ip100a
and ip100 is in phy. We can use one driver to support those two device, I
want
to know what is better for kernel:
1. Only updata sundance.c to support IP100A
2. Release ip100a.c which support ip100(sundance) to kernel 2.6.x and ask to
remove sundance.c.
3. Release ip100a.c with sundance.c both to kernel 2.6.x
We hope to use IP100a.c as our product driver, so 2. and 3. will better for
IC Plus. But we will still follow your suggestion, if you feel 1. was better
for kernel.
Jesse
----- Original Message -----
From: "John W. Linville" <[EMAIL PROTECTED]>
To: "Jesse Huang" <[EMAIL PROTECTED]>
Cc: <linux-kernel@vger.kernel.org>; <netdev@vger.kernel.org>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, July 27, 2006 8:54 PM
Subject: Re: [PATCH] Create IP100A Driver
On Thu, Jul 27, 2006 at 03:54:25PM -0400, Jesse Huang wrote:
> From: Jesse Huang <[EMAIL PROTECTED]>
>
> This is the first version of IP100A Linux Driver.
One general comment is that your patch is whitespace-damaged,
undoubtedly mangled by your mailer. I would suggest that you use
a text- or curses-based mailer (like mutt or even mail) for sending
patches, but I'm sure there are graphical mailers that can be trained
to not be "too smart".
> +static struct pci_device_id ipf_pci_tbl[] __devinitdata = {
> + {0x1186, 0x1002, 0x1186, 0x1002, 0, 0, 0},
> + {0x1186, 0x1002, 0x1186, 0x1003, 0, 0, 1},
> + {0x1186, 0x1002, 0x1186, 0x1012, 0, 0, 2},
> + {0x1186, 0x1002, 0x1186, 0x1040, 0, 0, 3},
> + {0x1186, 0x1002, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 4},
> + {0x13F0, 0x0201, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 5},
> + {0x13F0, 0x0200, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 6},
> + {0,}
> +};
This PCI ID table is identical to the one in the sundance driver.
What advantage does this driver offer over sundance?
Thanks,
John
--
John W. Linville
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
