linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Bombe <andreas.bombe@munich.netsurf.de>
To: Albrecht Dreß <ad@mpifr-bonn.mpg.de>
Cc: FireWire devel <linux1394-devel@eclipt.uni-klu.ac.at>,
	LinuxPPC-Dev Liste <linuxppc-dev@lists.linuxppc.org>
Subject: Re: FireWire + Apple PB G3: some success
Date: Thu, 24 Feb 2000 00:58:39 +0100	[thread overview]
Message-ID: <20000224005839.A2784@storm.local> (raw)
In-Reply-To: <38B3B564.CBA71EC0@mpifr-bonn.mpg.de>; from ad@mpifr-bonn.mpg.de on Wed, Feb 23, 2000 at 11:24:36AM +0100


On Wed, Feb 23, 2000 at 11:24:36AM +0100, Albrecht Dreß wrote:
> I had some success with Newer Tech's FireWire2Go CardBus device on an Apple
> PowerBook G3/333 (aka "Lombard") with LinuxPPC 2.2.14pre9.  This is what I did:
>
> * added Ryuichi Oikawa patch to the kernel which enables the pci scan to "see"
> CardBus devices without the PCMCIA package (there is a japanese description at
> http://www.rr.iij4u.or.jp/~roikawa/others.html [which I can't read], but the
> patch seems to work really fine)

Nice.  So CardBus devices do act like normal PCI devices (except for
scanning, apparantly).

>          lynx->id = num_of_cards-1;
>          lynx->dev = dev;
>
> -        pci_set_master(dev);
> +       pci_read_config_word (dev, PCI_COMMAND, &w);
> +       pci_write_config_word (dev, PCI_COMMAND, w | PCI_COMMAND_MASTER |
> PCI_COMMAND_MEMORY | PCI_COMMAND_IO);
>
>          if (!request_irq(dev->irq, lynx_irq_handler, SA_SHIRQ,
>                           PCILYNX_DRIVER_NAME, lynx)) {

I see.  That's the missing pci_enable_device() biting us.  But at least
in 2.2 there is no such function anyway, so it has to be done by hand.

> * `modprobe pcilynx' gives the following kernel messages:
>
[...]
> kernel: pcilynx0: resetting bus on request
> kernel: ieee1394: detected 1 pcilynx adapter

The messages for bus reset completion are missing, so it only works
partly.

> * remaining questions:
>
> I have a FW disk attached to the bus, but when I run testlibraw, it is not seen:

It's not seen because the driver is stuck in bus reset.  The most
probable reason is that DMA is not working.  I can't think of a reason
right now (since it does work on another PPC).

--
          Andreas E. Bombe <andreas.bombe@munich.netsurf.de>
http://home.pages.de/~andreas.bombe/                DSA key 0x04880A44

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-02-23 23:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-23 10:24 FireWire + Apple PB G3: some success Albrecht Dre_
2000-02-23 23:58 ` Andreas Bombe [this message]
2000-02-24  2:44   ` [Linux1394-devel] " Maxim S. Shatskih
2000-02-24 16:17     ` Andreas Bombe
2000-02-28 12:59       ` Albrecht Dre_
2000-02-28 19:02         ` Andreas Bombe
2000-02-29 16:07         ` Ryuichi Oikawa
2000-02-29 16:45           ` Benjamin Herrenschmidt
2000-03-02 17:22             ` Ryuichi Oikawa
2000-03-01  7:30           ` Albrecht Dre_
  -- strict thread matches above, loose matches on Subject: below --
2000-03-03 10:07 Benjamin Herrenschmidt
2000-03-03 19:46 Dan Bethe

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=20000224005839.A2784@storm.local \
    --to=andreas.bombe@munich.netsurf.de \
    --cc=ad@mpifr-bonn.mpg.de \
    --cc=linux1394-devel@eclipt.uni-klu.ac.at \
    --cc=linuxppc-dev@lists.linuxppc.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).