From: Michael Schmitz <schmitzmic@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Debian m68k <debian-68k@lists.debian.org>
Subject: Re: Status of the FB drivers on m68k
Date: Sat, 14 Oct 2017 04:45:02 +1300 [thread overview]
Message-ID: <f65ab00c-8dad-f7a4-cba8-14c6d9fe3ce8@gmail.com> (raw)
In-Reply-To: <90f7b321-207c-fd6d-92ae-f415a7fcf384@physik.fu-berlin.de>
Hi Adrian,
>> For CyberVision 64, CyberVision 64/3D, and Retina/Z3, the amount of work
>> shouldn't be that big. Just revert commit e019630e78e3482c, and look how
>> other fbdev driver were converted to the new framework.
>
> Alright. I hope you, Michael Schmitz and Michael Karcher will be around
Take a look at commit a100501212f2e26bb6d70bfb5c55eefd90e22b65 for the
initial conversion please (use -b -w to cut down on whitespace changes
shown). Warning: lots of formatting changes make this quite hard to follow.
I'm sure I looked at changes to amifb.c to figure out how the fbdev
interface had changed. Haven't found that in current git history but it
should be in the full history tree.
> Ok, I guess the next things to be done then are:
>
> - Michael Schmitz' ESP driver fixes for the Cyberstorm SCSI
Finn's fixes actually, and no guarantee what I have in mind will
actually work.
> - Michael Karcher's xsurf100 driver
> - fixing Cybervision 64, 64/3D, Retina Z3
>
> Might also be an idea to have another Linux/m68k meeting to
> get these things done :-).
I won't be back in Europe before July next...
Cheers,
Michael
next prev parent reply other threads:[~2017-10-13 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 18:32 Status of the FB drivers on m68k John Paul Adrian Glaubitz
2017-10-11 7:24 ` Geert Uytterhoeven
2017-10-11 11:09 ` Christian T. Steigies
2017-10-11 12:01 ` John Paul Adrian Glaubitz
2017-10-13 15:45 ` Michael Schmitz [this message]
2017-10-14 2:23 ` Finn Thain
2017-10-14 6:40 ` John Paul Adrian Glaubitz
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=f65ab00c-8dad-f7a4-cba8-14c6d9fe3ce8@gmail.com \
--to=schmitzmic@gmail.com \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@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