mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arno Griffioen <arno@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jean-Luc Leger <reiga@dspnet.fr.eu.org>,
	Arno Griffioen <arno.griffioen@ieee.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: CONFIG_GG2 (was: Re: Some kconfig issues)
Date: Mon, 5 Dec 2005 07:27:50 +0100	[thread overview]
Message-ID: <20051205062750.GA2398@attic.nerdnet.nl> (raw)
In-Reply-To: <Pine.LNX.4.62.0512042237520.15120@pademelon.sonytel.be>

On Sun, Dec 04, 2005 at 10:49:42PM +0100, Geert Uytterhoeven wrote:
> > GG2 in arch/m68k/Kconfig
> 
> Indeed, Amiga Golden Gate II Zorro/ISA bridge support is only partially there,
> and cannot be selected.
> 
> Arno, do we still miss a lot?

No, not as far as I know.. I'll try to build 2.6 on my Amiga with the GG
card soon and post the driver ont he list.

The 'driver' (if you can call it that) for the card pretty much does nothing 
anymore, just flip some bits on the card to enable it's interrupt forwarding and
enabling or disabling the waitstates on the ISA BUS.

Because most i386/ISA drivers these days can handle shared/chained interrupt
handlers like we always had on the m68k it's no longer needed to set up a
secondary IRQ handling for the ISA drivers. (like I had to do for 2.2)

After that it's just a matter of some macro's for the byte-swapping of
the ISA data and the address mangling for accessing the I/O and memory space.

Of course no DMA support and such, so no need to mess with that..

							Bye, Arno.

      reply	other threads:[~2005-12-05  6:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03 19:52 Some kconfig issues Jean-Luc Leger
2005-12-04 21:49 ` CONFIG_GG2 (was: Re: Some kconfig issues) Geert Uytterhoeven
2005-12-05  6:27   ` Arno Griffioen [this message]

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=20051205062750.GA2398@attic.nerdnet.nl \
    --to=arno@linux-m68k.org \
    --cc=arno.griffioen@ieee.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=reiga@dspnet.fr.eu.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

all inboxes | Powered by JetHome®