linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>
To: Joseph Wenninger <jowenn@kde.org>
Cc: linux-kernel@vger.kernel.org, robn@verdi.et.tudelft.nl
Subject: Re: usb CF reader and 2.4.19
Date: Wed, 16 Oct 2002 17:34:00 +0200	[thread overview]
Message-ID: <200210161534.g9GFY0508740@verdi.et.tudelft.nl> (raw)
In-Reply-To: Message from Joseph Wenninger <jowenn@kde.org>  of "16 Oct 2002 11:22:04 +0200." <1034760128.1306.4.camel@jowennmobile>


Hi Joseph,

You don't mention what USB device you are using with your compact flash.
I don't have any problems with a "SanDisk Imagemate, SDDR-31" USB
CF reader: works flawlessly.

I'm using a up-to-date Red Hat 7.3 system with Red Hat kernel 2.4.18-10.
Maybe the driver(s) for your USB and/or cardreader are buggy.

	greetings,
	Rob van Nieuwkerk

PS: before chosing the SDDR-31 I did some extensive web-research on the
    USB/CF readers available with Linux.  I chose the SDDR-31 (which
    can be a bit hard to get nowadays) because it seemed the device
    with the least (Linux) problems.

> Is there anything I can do to flush all usb / usb storage buffers to my
> compact flash ? 
> 
> At the moment I have to rmmod usb-storage && rmmod usb-uhci && modprobe
> usb-uhci && modprobe usb-storage to ensure all data is written
> correctly, otherwise the directory structure isn't saved even after an
> unmount.
> 
> Is there an application, function call, ioctl, .... which I can use,
> instead of the above mentioned inconvenient way ?
> 
> Kind regards
> Joseph Wenninger

  reply	other threads:[~2002-10-16 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16  9:22 usb CF reader and 2.4.19 Joseph Wenninger
2002-10-16 15:34 ` Rob van Nieuwkerk [this message]
2002-10-16 15:34 ` Greg KH
2002-10-16 17:16   ` Joseph Wenninger
     [not found] <no.id>
2002-10-16 21:10 ` Vid Strpic

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=200210161534.g9GFY0508740@verdi.et.tudelft.nl \
    --to=robn@verdi.et.tudelft.nl \
    --cc=jowenn@kde.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).