public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>
Cc: Petr Stehlik <pstehlik@sophics.cz>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k: Fix atarimouse init
Date: Sat, 03 Jan 2009 09:45:26 +0100	[thread overview]
Message-ID: <jek59cg4m1.fsf@sykes.suse.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0901030758590.17350@zirkon.biophys.uni-duesseldorf.de> (Michael Schmitz's message of "Sat, 03 Jan 2009 08:23:20 +0100 (CET)")

Michael Schmitz <schmitz@biophys.uni-duesseldorf.de> writes:

> That may have been the reason, perhaps before the mouse driver was written to 
> the busmouse interface (not sure I have kernel sources dating that far back).

You can get historical sources from
<git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git>.  Tag
v2.5.41 is the last one containing the old atarimouse driver.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-01-03  8:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081217165557.b4898a4b.sfr@canb.auug.org.au>
2008-12-17  8:18 ` linux-next: boot-params tree build failure Geert Uytterhoeven
2008-12-21 11:12   ` [PATCH] m68k: Kill several external declarations in source files (was: Re: linux-next: boot-params tree build failure) Geert Uytterhoeven
2008-12-21 22:21     ` Rusty Russell
2008-12-22  7:30       ` Geert Uytterhoeven
2008-12-28 22:00     ` [PATCH] m68k: Fix atarimouse init Michael Schmitz
2008-12-29 10:57       ` Geert Uytterhoeven
2008-12-30  9:18         ` Petr Stehlik
2009-01-02  0:27           ` Michael Schmitz
2009-01-02  0:12         ` Michael Schmitz
2009-01-02  9:42           ` Andreas Schwab
2009-01-02 10:20             ` Petr Stehlik
2009-01-02 22:10             ` Michael Schmitz
2009-01-03  5:53               ` Petr Stehlik
2009-01-03  6:15                 ` Petr Stehlik
2009-01-03  7:23                 ` Michael Schmitz
2009-01-03  8:16                   ` Petr Stehlik
2009-01-04  3:12                     ` Michael Schmitz
2009-01-04  7:34                       ` Petr Stehlik
2009-01-04  7:15                     ` [PATCH] m68k: Add Eiffel PS/2 support for Atari mouse driver Michael Schmitz
2009-01-04  7:41                       ` Petr Stehlik
2009-01-04 21:50                         ` Michael Schmitz
2009-01-04 22:10                           ` Petr Stehlik
2009-01-05  1:11                             ` Michael Schmitz
2009-01-05  1:32                       ` [PATCH] m68k: Add Eiffel PS/2 support for Atari mouse driver (updated) Michael Schmitz
2009-01-03  8:45                   ` Andreas Schwab [this message]
2009-01-04  2:05                     ` [PATCH] m68k: Fix atarimouse init Michael Schmitz

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=jek59cg4m1.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=pstehlik@sophics.cz \
    --cc=schmitz@biophys.uni-duesseldorf.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