From: Daniel Phillips <email@example.com> To: Dave Olien <firstname.lastname@example.org>, "David S. Miller" <email@example.com> Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: DAC960 in 2.5.38, with new changes Date: Tue, 24 Sep 2002 19:39:50 +0200 [thread overview] Message-ID: <E17ttf4-0003iY-00@starship> (raw) In-Reply-To: <20020924095456.A17658@acpi.pdx.osdl.net> On Tuesday 24 September 2002 18:54, Dave Olien wrote: > I haven't been ignoring the discussion. Just thinking it over. > I was going to dig out an old PCI spec last night, but got involved > with other things. I wanted to review how 64-bit PCI and 32-bit PCI busses > handle 32 and 64-bit writes from the processor. > > I don't have a spec for these controllers. IBM is selling Mylex > to LSI logic, so "All contracts, NDA's and agreements are on hold > until a transition to lsi is complete" Note: I will sign an NDA to get the specs for this card (family) but I would much prefer that somebody gets a clue and just releases the spec. Frankly, this board needs all the help it can get, based on comparative performance. Keeping the spec secret is just a brilliant way to ensure it will die, and thus be worth $0.00 to the purchaser. (I sincerely hope somebody in the DAC960 food chain notices this comment, or somebody forwards it to one of the aforementioned: give the world the spec and we will reciprocate by making the thing go as fast as theoretically possible.) Daniel
next prev parent reply other threads:[~2002-09-24 17:41 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-23 19:04 Dave Olien 2002-09-23 19:19 ` David Mosberger 2002-09-23 20:40 ` David S. Miller 2002-09-23 20:53 ` David Mosberger 2002-09-23 20:57 ` David S. Miller 2002-09-23 21:24 ` David Mosberger 2002-09-23 21:17 ` David S. Miller 2002-09-23 21:32 ` David Mosberger 2002-09-23 21:28 ` David S. Miller 2002-09-23 21:31 ` Daniel Phillips 2002-09-23 21:33 ` David Mosberger 2002-09-23 21:28 ` David S. Miller 2002-09-23 21:40 ` Daniel Phillips 2002-09-23 21:45 ` David Mosberger 2002-09-23 20:44 ` Daniel Phillips 2002-09-23 20:54 ` David S. Miller 2002-09-24 16:54 ` Dave Olien 2002-09-24 17:11 ` David Mosberger 2002-09-24 17:28 ` Dave Olien 2002-09-24 18:21 ` David Mosberger 2002-09-24 18:25 ` Dave Olien 2002-09-24 19:12 ` David Mosberger 2002-09-24 18:45 ` Dave Olien 2002-09-24 17:50 ` Daniel Phillips 2002-09-24 18:27 ` David Mosberger 2002-09-24 17:39 ` Daniel Phillips [this message] 2002-09-25 22:20 ` DAC960, documentation links Daniel Phillips 2002-09-25 22:23 ` Daniel Phillips 2002-09-26 0:02 ` Mr. James W. Laferriere 2002-09-26 16:13 ` DAC960 in 2.5.38, with new changes Alan Cox 2002-09-24 17:45 ` Daniel Phillips 2002-09-25 21:42 ` davide.rossetti 2002-09-23 20:39 ` Daniel Phillips 2002-09-23 21:41 ` Dave Olien 2002-09-23 21:53 ` Daniel Phillips 2002-09-23 22:03 ` Dave Olien 2002-09-23 22:22 ` Daniel Phillips
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=E17ttf4-0003iY-00@starship \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: DAC960 in 2.5.38, with new changes' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).