* Re: What is current sundance.c status [not found] <004301c6eda6$437ac070$2d32fea9@icplus.com.tw> @ 2006-10-12 2:55 ` Andrew Morton 2006-10-13 1:14 ` Jesse Huang 0 siblings, 1 reply; 2+ messages in thread From: Andrew Morton @ 2006-10-12 2:55 UTC (permalink / raw) To: Jesse Huang; +Cc: linux-kernel, netdev, jgarzik On Thu, 12 Oct 2006 10:29:37 +0800 "Jesse Huang" <jesse@icplus.com.tw> wrote: > Would you tell me what is the current IP100A status? Should I re-generate patches again. Would it put into kernel or not? I'm sitting on a copy of them. I didn't send them to Jeff last time because: sundance-remove-txstartthresh-and-rxearlythresh.patch There's no description of what this patent issue is. sundance-fix-tx-pause-bug-reset_tx-intr_handler.patch There's no description of the bug which got fixed, nor how this patch fixes it. sundance-change-phy-address-search-from-phy=1-to-phy=0.patch There's a (small) possibility that this will break on hardware which _doesn't_ have a phy at address 0. sundance-correct-initial-and-close-hardware-step.patch There's no real description of the bug which is being fixed, nor of how this patch fixes it. sundance-solve-host-error-problem-in-low-performance-embedded.patch No description of what the "host error problem" is, nor of what causes it, nor of how this patch fixes it. So generally these patches are a bit worrying, and it is hard to gauge what their risk factor is. ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: What is current sundance.c status 2006-10-12 2:55 ` What is current sundance.c status Andrew Morton @ 2006-10-13 1:14 ` Jesse Huang 0 siblings, 0 replies; 2+ messages in thread From: Jesse Huang @ 2006-10-13 1:14 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, netdev, jgarzik Ok, I will generate those again with descriptions. Thank you! Best Regards, Jesse Huang. ----- Original Message ----- From: "Andrew Morton" <akpm@osdl.org> To: "Jesse Huang" <jesse@icplus.com.tw> Cc: <linux-kernel@vger.kernel.org>; <netdev@vger.kernel.org>; <jgarzik@pobox.com> Sent: Thursday, October 12, 2006 10:55 AM Subject: Re: What is current sundance.c status On Thu, 12 Oct 2006 10:29:37 +0800 "Jesse Huang" <jesse@icplus.com.tw> wrote: > Would you tell me what is the current IP100A status? Should I re-generate patches again. Would it put into kernel or not? I'm sitting on a copy of them. I didn't send them to Jeff last time because: sundance-remove-txstartthresh-and-rxearlythresh.patch There's no description of what this patent issue is. sundance-fix-tx-pause-bug-reset_tx-intr_handler.patch There's no description of the bug which got fixed, nor how this patch fixes it. sundance-change-phy-address-search-from-phy=1-to-phy=0.patch There's a (small) possibility that this will break on hardware which _doesn't_ have a phy at address 0. sundance-correct-initial-and-close-hardware-step.patch There's no real description of the bug which is being fixed, nor of how this patch fixes it. sundance-solve-host-error-problem-in-low-performance-embedded.patch No description of what the "host error problem" is, nor of what causes it, nor of how this patch fixes it. So generally these patches are a bit worrying, and it is hard to gauge what their risk factor is. ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-10-13 1:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <004301c6eda6$437ac070$2d32fea9@icplus.com.tw>
2006-10-12 2:55 ` What is current sundance.c status Andrew Morton
2006-10-13 1:14 ` Jesse Huang
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox