mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mogens Valentin <mogensv@vip.cybercity.dk>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ahci: get JMicron JMB360 working
Date: Sun, 29 Jan 2006 19:24:16 +0100	[thread overview]
Message-ID: <43DD0850.8090705@vip.cybercity.dk> (raw)
In-Reply-To: <200601291016.30459.prakash@punnoor.de>

Prakash Punnoor wrote:
> Am Sonntag Januar 29 2006 06:04 schrieb Jeff Garzik:
> 
> 
>>This patch, against latest 2.6.16-rc-git, adds support for JMicron and
>>fixes some code that should be Intel-only, but was being executed for
>>all vendors.
> 
> 
> Thx, works nicely here with JMicron jMB360 on an Asrock board.

Interesting. On 111105, I wrote to Asrock about Linux libata support for 
JM360, and mentioned Jeff Garzik as the developer/maintainer, along with 
his requirements for implementing JM360 libata support, but never got a 
reply from Asrock. I didn't get back to Garzik either; my apologies...

Due to other work, I didn't go on with that mobo, and partly because I 
saw no other products using JM360.
Nvidia hving bought ULi, I wonder what'll happen to ILi and Asrock.
I know that (fabless) Jmicron does chipset design and integration.

939Dual-SATA2 is interesting as an upgrade board due to performance, 
price, working PCIe/AGP and provisions for socket M2 via an adapter.
Whether this will actually work is of cause to be seen...
Now having libata SATA support gets it back into my thoughts.

@Prakash: Did you test with a SATA-2 disk?

-- 
Kind regards,
Mogens Valentin


  reply	other threads:[~2006-01-29 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29  5:04 Jeff Garzik
2006-01-29  9:16 ` Prakash Punnoor
2006-01-29 18:24   ` Mogens Valentin [this message]
2006-01-29 22:27     ` Prakash Punnoor
2006-01-29 11:01 ` Norbert Kiesel
2006-01-29 13:43   ` Prakash Punnoor

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=43DD0850.8090705@vip.cybercity.dk \
    --to=mogensv@vip.cybercity.dk \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakash@punnoor.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

all inboxes | Powered by JetHome®