linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: trash can <thetrashcan@earthlink.net>
Cc: Robert Hancock <hancockr@shaw.ca>,
	linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>
Subject: Re: Iomega ZIP-100 drive unsupported with jmicron JMB361 chip?
Date: Tue, 11 Dec 2007 14:30:40 -0500	[thread overview]
Message-ID: <475EE560.6040601@rtr.ca> (raw)
In-Reply-To: <475EDF76.4000703@earthlink.net>

trash can wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Thanks for the note. Zip drive as only device on the bus did not work
> for me. kernel is correctly identifying the Jmicron chip.
..

So have you tried 2.6.24-rc* on that system yet, using only libata ?

> Mark Lord wrote:
>> Mark Lord wrote:
>>> I missed the early part of this thread,
>>> but here is a data point that may or may not be useful.
>>>
>>> I have an ASUS mobo here with an onboard JM363 SATA/PATA controller
>>> (verified by looking at the actual chip).
>>>
>>> It works fine when in AHCI mode with a PATA ATAPI ZIP100 drive
>>> all by itself.  No other configurations tested.
>>> This is with kernel 2.6.24-rc4-git?.
>> ..
>>
>> Oh yeah.. that's with libata controlling all drives in the system.
..

  reply	other threads:[~2007-12-11 19:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.yONLBG7CMuz80f4dUP5r/5k7emw@ifi.uio.no>
2007-12-11  0:21 ` Iomega ZIP-100 drive unsupported with jmicron JMB361 chip? Robert Hancock
2007-12-11 15:38   ` trash can
2007-12-11 16:54     ` Mark Lord
2007-12-11 16:57       ` Mark Lord
2007-12-11 19:05         ` trash can
2007-12-11 19:30           ` Mark Lord [this message]
2007-12-12 19:23             ` trash can
2007-12-17  0:50               ` Bill Davidsen
2007-12-15  4:31             ` trash can
2007-12-10 20:09 trash can
2007-12-17  9:00 ` Andrew Morton

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=475EE560.6040601@rtr.ca \
    --to=liml@rtr.ca \
    --cc=hancockr@shaw.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thetrashcan@earthlink.net \
    /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;
as well as URLs for NNTP newsgroup(s).