Hi John, hi Artem, hi Michael.
John Paul Adrian Glaubitz - 13.06.23, 09:22:52 CEST:
> On Tue, 2023-06-13 at 09:20 +0200, Martin Steigerwald wrote:
> > John Paul Adrian Glaubitz - 13.06.23, 08:47:11 CEST:
> > > I was wondering what the current status of the affs driver in the
&g
Thanks for your reply, Michael. And all your efforts to get the patch in.
Michael Schmitz - 13.06.23, 09:58:09 CEST:
> Am 13.06.2023 um 19:20 schrieb Martin Steigerwald:
> > John Paul Adrian Glaubitz - 13.06.23, 08:47:11 CEST:
> >> I was wondering what the current status of the
Hi Martin,
Am 13.06.2023 um 19:20 schrieb Martin Steigerwald:
John Paul Adrian Glaubitz - 13.06.23, 08:47:11 CEST:
I was wondering what the current status of the affs driver in the
kernel is, did it receive the fixes that Michael(?) was working on? I
vaguely remember there were some issues
Check out the format section... it will create filesystems:
https://amitools.readthedocs.io/en/latest/tools/xdftool.html
I haven't tried it directly on a drive as opposed to an image but there's a
good likelihood it might just work.
On Tue, Jun 13, 2023, 12:21 AM John Paul Adrian Glaubitz <
glaub
Hi Martin!
On Tue, 2023-06-13 at 09:20 +0200, Martin Steigerwald wrote:
> John Paul Adrian Glaubitz - 13.06.23, 08:47:11 CEST:
> > I was wondering what the current status of the affs driver in the
> > kernel is, did it receive the fixes that Michael(?) was working on? I
> > v
Hi Stefan!
On Tue, 2023-06-13 at 00:15 -0700, Stefan Reinauer wrote:
> I have found amitools from Christian Vogelgsang to be a good tool
> for creating and manipulating affs.
Looks interesting [1] but it doesn't seem to contain any tool for
creating and checking AFFS filesystems.
Adrian
> [1] h
John Paul Adrian Glaubitz - 13.06.23, 08:47:11 CEST:
> I was wondering what the current status of the affs driver in the
> kernel is, did it receive the fixes that Michael(?) was working on? I
> vaguely remember there were some issues with larger filesystems or so
> and that someone wa
On Tue, 2023-06-13 at 08:47 +0200, John Paul Adrian Glaubitz wrote:
> Also, I noticed that Roman Zippel actually created an affstools package [1]
> back in the day and I wonder whether anyone has any experience with it. In
> particular, I'm wondering what »different mkfs.affs« Artem Bityutskiy is
>
I have found amitools from Christian Vogelgsang to be a good tool for
creating and manipulating affs.
On Mon, Jun 12, 2023, 11:47 PM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hello!
>
> I was wondering what the current status of the affs driver in the ker
Hi Artem!
On Tue, 2023-06-13 at 09:53 +0300, Artem Bityutskiy wrote:
> I apologize, that message was sent 10 years ago and I do not remember details
> any longer.
No worries, thanks for the quick reply!
> What I do remember is that I was doing some cross-filesystem changes and
> struggled to tes
Hello!
I was wondering what the current status of the affs driver in the kernel is,
did it receive the fixes that Michael(?) was working on? I vaguely remember
there were some issues with larger filesystems or so and that someone was
working on fixing these issues.
Also, I noticed that Roman
Please answer to pkg-rust-maintain...@lists.alioth.debian.org. Don't answer
to debian-ports@l.d.o (just let your mail client honor the Reply-To field).
Hello!
I would like to a quick heads-up regarding the architecture status of Rust
after having had at the possibilities to get it bootstr
You guys rock :) Thank´s for you work!
Harald
-Ursprüngliche Nachricht-
Von: John Paul Adrian Glaubitz [mailto:glaub...@physik.fu-berlin.de]
Gesendet: Samstag, 14. Oktober 2017 08:40
An: Finn Thain
Cc: Michael Schmitz; Geert Uytterhoeven; Linux/m68k; Debian m68k
Betreff: Re: Status of
> On Oct 14, 2017, at 4:23 AM, Finn Thain wrote:
>
> On Sat, 14 Oct 2017, Michael Schmitz wrote:
>
>>> - Michael Schmitz' ESP driver fixes for the Cyberstorm SCSI
>>
>> Finn's fixes actually, and no guarantee what I have in mind will
>> actually work.
>>
>
> Just to clarify, Michael and I
On Sat, 14 Oct 2017, Michael Schmitz wrote:
> > - Michael Schmitz' ESP driver fixes for the Cyberstorm SCSI
>
> Finn's fixes actually, and no guarantee what I have in mind will
> actually work.
>
Just to clarify, Michael and I did reach a solution (i.e. don't attempt
2-byte DMA transfers) aft
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
Hi Geert!
On 10/11/2017 09:24 AM, Geert Uytterhoeven wrote:
I am currently discussing the topic of usable graphics cards on Debian/m68k
on the German Amiga forum a1k.org since one user asked me [1] and he told
me that in the past, users could use CONFIG_FB_CYBER and CONFIG_FB_VIRGE
which both se
Moin,
On Wed, Oct 11, 2017 at 09:24:57AM +0200, Geert Uytterhoeven wrote:
> On Tue, Oct 10, 2017 at 8:32 PM, John Paul Adrian Glaubitz
>
> > Is there a chance to bring the CYBER and VIRGE drivers back? And maybe
> > get PM2 working on m68k?
>
> There's always a chance ;-)
> You "just" need someon
Hi Adrian,
On Tue, Oct 10, 2017 at 8:32 PM, John Paul Adrian Glaubitz
wrote:
> Does anyone of the kernel guys, especially Geert, know what the current status
> of the framebuffer drivers on m68k is?
>
> I am currently discussing the topic of usable graphics cards on Debian/m68k
>
Hi!
Does anyone of the kernel guys, especially Geert, know what the current status
of the framebuffer drivers on m68k is?
I am currently discussing the topic of usable graphics cards on Debian/m68k
on the German Amiga forum a1k.org since one user asked me [1] and he told
me that in the past
rently have 6 machines up
> with remote power and remote console (of course that being development
> boards is not so nice as server remote management goodies). Some
> machines require a button press but local admins are great and always
> happy to help.
>
> If none steps up explain
On Mon, Jun 27, 2016 at 04:35:03PM +0200, Wouter Verhelst wrote:
> (sorry for jumping in late here)
>
> On Wed, Jun 15, 2016 at 07:51:55AM +0800, Paul Wise wrote:
> > On Wed, 2016-06-15 at 01:37 +0300, Dimitri John Ledkov wrote:
> >
> > > At the openmainframeproject EU meetup, it was indicated th
(sorry for jumping in late here)
On Wed, Jun 15, 2016 at 07:51:55AM +0800, Paul Wise wrote:
> On Wed, 2016-06-15 at 01:37 +0300, Dimitri John Ledkov wrote:
>
> > At the openmainframeproject EU meetup, it was indicated that SUSE
> > joined with indication that Open Build Service might be able to u
On Mon, Jun 20, 2016 at 10:35:20PM +0200, Geert Uytterhoeven wrote:
> Yeah, apparently it's cheaper to bootstrap a complete new little endian
> platform than to fix portability issues in existing software...
I believe a big reason is that Nvidia cards expect little endian data,
and the overhead of
On Mon, Jun 20, 2016 at 8:32 PM, Nelson H. F. Beebe wrote:
> Recent traffic on this list has discussed Debian on PowerPC and
> big-endian vs little-endian.
>
> The next-generation US national laboratory facilities are to be based
> on PowerPC, and one source that I read mentioned little-endian, li
Recent traffic on this list has discussed Debian on PowerPC and
big-endian vs little-endian.
The next-generation US national laboratory facilities are to be based
on PowerPC, and one source that I read mentioned little-endian, likely
for binary file compatibility with files produced on Intel x86 a
On 2016-06-20 10:29, John Paul Adrian Glaubitz wrote:
On 06/20/2016 04:15 PM, Lennart Sorensen wrote:
On Mon, Jun 20, 2016 at 04:11:32PM +0200, John Paul Adrian Glaubitz
wrote:
Well, we just did a full archive rebuild of "ppc64" to be able to
support ppc64 on the e5500 cores by disabling AltiVe
On 06/20/2016 04:15 PM, Lennart Sorensen wrote:
> On Mon, Jun 20, 2016 at 04:11:32PM +0200, John Paul Adrian Glaubitz wrote:
>> Well, we just did a full archive rebuild of "ppc64" to be able to
>> support ppc64 on the e5500 cores by disabling AltiVec, didn't we?
>
> Well it is getting there.
The
On Mon, Jun 20, 2016 at 04:11:32PM +0200, John Paul Adrian Glaubitz wrote:
> Well, we just did a full archive rebuild of "ppc64" to be able to
> support ppc64 on the e5500 cores by disabling AltiVec, didn't we?
Well it is getting there.
--
Len Sorensen
On 06/20/2016 04:05 PM, Lennart Sorensen wrote:
> Also I suspect many users of 64 bit capable freescale chips
> (e5500 and e6500 cores) are running 32 bit powerpc since they
> don't have enough ram to actually really gain anything
> from going to 64 bit, and the ppc64 port isn't done yet.
Well, we
On Sun, Jun 19, 2016 at 08:35:02PM +0200, Florian Weimer wrote:
> Do they implement the ISA required by the existing Debian port?
Yes.
The only ones that don't are the Freescale 85xx and P10[12]x chips,
which are powerpcspe due to using the e500 core.
All the 83xx and 82xx chips which are still
* Lennart Sorensen:
> There are a lot of 32bit powerpc chips still going into embedded systems
> being built today. They are not going away anytime soon.
Do they implement the ISA required by the existing Debian port?
> In other words, i don't think a s390x box will ever just die.
I'm sure “death” encompasses all events which might lead Debian to
lose access to relevant hardware. It's not just about faults with a
piece of equipment.
On 19 June 2016 at 02:25, William ML Leslie
wrote:
>
> In case it isn't clear, the number of users of the architecture is not part
> of the qualification, it is the amount of maintenance pressure involved.
> Package maintainers have to put more effort into ensuring builds succeed for
> release
On 06/18/2016 06:25 PM, William ML Leslie wrote:
> In case it isn't clear, the number of users of the architecture is not part
> of the qualification, it is the amount of maintenance pressure involved.
> Package
> maintainers have to put more effort into ensuring builds succeed for release
> arc
In case it isn't clear, the number of users of the architecture is not part
of the qualification, it is the amount of maintenance pressure involved.
Package maintainers have to put more effort into ensuring builds succeed
for release architectures, which detracts from other work that needs to be
do
I run all sorts of PowerPC machines with various versions of Debian and I
don't see that coming to end anytime soon. These are excellent and
reliable machines. Biggest issues/hurdles are just graphics at the moment
for both ATI/AMD and Nvidia cards, but even if that is never resolved/fixed
or per
Hi,
Dan DeVoto wrote:
In addition to the debian powerpc mailing list, powerpc users are active on the
Ubuntu forums. I'm running Debian Sid on a Powerbook and everything works
except 3D acceleration. I don't see a need to drop it.
I hope that my iBook G3 will serve me for years to come! Lo
On Thu, Jun 16, 2016 at 09:04:12AM +0200, Mathieu Malaterre wrote:
> The debian-powerpc@l.d.o mailing list is active so I would say it
> still has some users. I have been using partch.d.o for doing some work
> on PowerPC. I posted a summary of work people have been doing on this
> port lately:
>
>
On 2016-06-15 00:37, Dimitri John Ledkov wrote:
There is openmainframe project https://www.openmainframeproject.org/ ,
which I believe offers access to z/VM instances hosted by Marist
colledge.
At the openmainframeproject EU meetup, it was indicated that SUSE
joined with indication that Open Bui
Here too all new amiga Ng are PPC with last generations of gpu pcie Amd boards
and we are using linux expecially Debian.
Luigi
From: herminio.hernande...@gmail.com
Date: Wed, 15 Jun 2016 22:02:29 -0700
Subject: Re: [Stretch] Status for architecture qualification
To: hector.o...@gmail.com
CC
Hi Hector,
On Thu, Jun 16, 2016 at 2:12 AM, Hector Oron wrote:
[...]
> While working out ArchitectureQualification/Stretch wiki page I
> believe everything is mostly fine for release, however I got a
> personal concern on powerpc architecture. Is it well maintained? Does
> it have porters? Does i
re hardware, we currently have 6 machines up
> with remote power and remote console (of course that being development
> boards is not so nice as server remote management goodies). Some
> machines require a button press but local admins are great and always
> happy to help.
>
> If none
and remote console (of course that being development
boards is not so nice as server remote management goodies). Some
machines require a button press but local admins are great and always
happy to help.
If none steps up explaining what are DSA concerns on the ARM
architectures, please update status
On Tue, Jun 14, 2016, at 18:37, Dimitri John Ledkov wrote:
>
> There is openmainframe project https://www.openmainframeproject.org/ ,
> which I believe offers access to z/VM instances hosted by Marist
> colledge.
>
> At the openmainframeproject EU meetup, it was indicated that SUSE
> joined with
On Wed, 2016-06-15 at 01:37 +0300, Dimitri John Ledkov wrote:
> At the openmainframeproject EU meetup, it was indicated that SUSE
> joined with indication that Open Build Service might be able to use
> resources hosted by Marist.
>
> I wonder if it makes sense to reach out, and see if there are
>
On 14 June 2016 at 20:22, wrote:
> On 2016-06-14 03:06, Philipp Kern wrote:
>>
>> On Mon, Jun 13, 2016 at 07:33:56PM +, Niels Thykier wrote:
>>>
>>> Philipp Kern:
>>> > On 2016-06-05 12:01, Niels Thykier wrote:
>>> >> * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
>>> >>
On 2016-06-14 03:06, Philipp Kern wrote:
On Mon, Jun 13, 2016 at 07:33:56PM +, Niels Thykier wrote:
Philipp Kern:
> On 2016-06-05 12:01, Niels Thykier wrote:
>> * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
>>s390x
>>- *No* blockers at this time from RT, DSA no
On 06/14/2016 09:06 AM, Philipp Kern wrote:
> Yeah, but that's unfortunately one of the universal truths of this port.
> I mean in theory sometimes they turn up on eBay and people try to make
> them work[1].
Hilarious talk, thanks a lot for the link :).
> It also seems true for other ports where
On 14/06/16 09:06, Philipp Kern wrote:
> On Mon, Jun 13, 2016 at 07:33:56PM +, Niels Thykier wrote:
>> Philipp Kern:
>>> On 2016-06-05 12:01, Niels Thykier wrote:
* amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
s390x
- *No* blockers at this time from RT
On Mon, Jun 13, 2016 at 07:33:56PM +, Niels Thykier wrote:
> Philipp Kern:
> > On 2016-06-05 12:01, Niels Thykier wrote:
> >> * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
> >>s390x
> >>- *No* blockers at this time from RT, DSA nor security.
> >>- s390, ppc64e
Philipp Kern:
> On 2016-06-05 12:01, Niels Thykier wrote:
>> * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
>>s390x
>>- *No* blockers at this time from RT, DSA nor security.
>>- s390, ppc64el and all arm ports have DSA concerns.
>
> What is the current DSA concern
On 2016-06-05 12:01, Niels Thykier wrote:
* amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
s390x
- *No* blockers at this time from RT, DSA nor security.
- s390, ppc64el and all arm ports have DSA concerns.
What is the current DSA concern about s390x?
Kind regards a
On 2016-06-05 8:56 AM, Steven Chamberlain wrote:
John Paul Adrian Glaubitz wrote:
>I have invested lots of time and effort to get sparc64 into a usable state in
Debian.
>We are close to 11.000 installed packages. Missing packages include Firefox,
>Thunderbird/Icedove, golang and LibreOffice to
Steven Chamberlain:
> Hi,
>
Hi,
> John Paul Adrian Glaubitz wrote:
>> I have invested lots of time and effort to get sparc64 into a usable state
>> in Debian.
>> We are close to 11.000 installed packages. Missing packages include Firefox,
>> Thunderbird/Icedove, golang and LibreOffice to name t
Hi,
On Sun, 2016-06-05 at 13:26 +0200, John Paul Adrian Glaubitz wrote:
> sh4:
>
>
> The two biggest issues with sh4 are currently with binutils and the
> kernel. binutils has problems when building Qt5:
>
There is in fact another big elephant in the room, which I have
mentioned several tim
thanks to everyone explaining arch:any to me :)
--
cheers,
Holger
signature.asc
Description: Digital signature
Hi,
John Paul Adrian Glaubitz wrote:
> I have invested lots of time and effort to get sparc64 into a usable state in
> Debian.
> We are close to 11.000 installed packages. Missing packages include Firefox,
> Thunderbird/Icedove, golang and LibreOffice to name the most important ones.
Is there so
John Paul Adrian Glaubitz:
> Hi Niels!
>
> On 06/05/2016 12:01 PM, Niels Thykier wrote:
>> Beyond mips64el, we are not aware of any new architectures for Stretch.
>>
>> I kindly ask you to:
>>
>> * Porters, please assert if your architecture is targeting Stretch.
>
> To give some insight what's
On 05/06/16 13:00, Holger Levsen wrote:
On Sun, Jun 05, 2016 at 01:26:39PM +0200, John Paul Adrian Glaubitz wrote:
ppc64:
This architecture is basically on par with the release architectures. We have
over
11.000 packages installed
[...]
sparc64:
We are close to 11.000 installed
I missing?
But around 12000 of those source packages only build Arch: all packages.
If you look at amd64's buildd stats in sid, there are ~12000 source
packages in the Installed state:
https://buildd.debian.org/status/architecture.php?a=amd64&suite=sid
i386 also has ~12000; arm64, arm
On 06/05/2016 02:00 PM, Holger Levsen wrote:
> I'm not sure whether you are talking about source or binary packages but
> sid/amd64 has over 24000 source packages and over 5 binary packages,
> so I would call the above "on par". Or what am I missing?
There are just around 12,000 source package
On Sun, Jun 05, 2016 at 01:26:39PM +0200, John Paul Adrian Glaubitz wrote:
> ppc64:
>
> This architecture is basically on par with the release architectures. We have
> over
> 11.000 packages installed
[...]
> sparc64:
> We are close to 11.000 installed packages.
I'm not sure whether you are tal
Hi Niels!
On 06/05/2016 12:01 PM, Niels Thykier wrote:
> Beyond mips64el, we are not aware of any new architectures for Stretch.
>
> I kindly ask you to:
>
> * Porters, please assert if your architecture is targeting Stretch.
To give some insight what's happening in Debian Ports. We have two c
Hi members of DSA, Security, RT and all porters.
While the freeze still seem far away, I think it is time to start with
the architecture qualifications.
For starters, here are the architectures we are aware of:
* amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
s390x
- *N
Hi all,
I'd like to provide you with an update for the linux-m68k.org services.
All linux-m68k.org services have been moved from nerdnet.nl to Gandi.
This includes:
1. The domain itself (this was already at Gandi before),
2. DNS (service included with the domain).
Old entries have been p
Make use of the ax88796 platform data interupt status hook in the
m68k Amiga XSurf100 driver. The XSurf100 interrupt is shared with
other Amiga hardware interrupts so ei_interrupt would otherwise
get called a lot without need.
Signed-off-by: Michael Karcher
Signed-off-by: Michael Schmitz
To be able to tell the ax88796 driver whether it is sensible to enter
the 8390 interrupt handler, an "is this interrupt caused by the 88796"
callback has been added to the ax_plat_data structure (with NULL being
compatible to the previous behaviour).
Signed-off-by: Michael Karcher
Signed-off-by:
John Voltz dixit:
>> # dselect update # or: apt-get update
>
> Trying either of these commands results in:
> E: The method driver /usr/lib/apt/methods/https could not be found.
Oh, this is bad of course.
Run this:
# printf ',g/naturalnet/d\nw\nq\n' | ed -s /etc/apt/sources.list
(Or just remove
Looks like I'll need to figure out how to get this and it's
(doubtless)
dozens of dependencies installed first.
Or you try my method instead which allows to choose the packages to be
included when invoking debootstrap using the --include option :-).
Adrian
I still don't have another hard d
On 06/01/2015 10:52 PM, John Voltz wrote:
> Looks like I'll need to figure out how to get this and it's (doubtless)
> dozens of dependencies installed first.
Or you try my method instead which allows to choose the packages to be
included when invoking debootstrap using the --include option :-).
A
Ok, removing my ZorRam card allows me to boot now. so I'm at step 11:
11) Install a few more packages. Now is a good time to add an
SSH server, and possibly your favourite editor (the image
has ed, jupp, and mcedit by default; you may wish to add
nano or vim-tiny if you like them, or joe-jupp fo
4a) Download it to where there is enough space (on the PC):
$ wget http://zigo.mirbsd.org:8080/t/2015-Jan/Ara2015A.tar.gz [1]
I attempted to use the pre-built image as you instructed, but ran into
problems after booting. See the attached boot log. It appears that I'm
having 68060 access erro
Geert Uytterhoeven dixit:
>But m68kboot (which includes amiboot, ataboot, etc.) seems to be in Debian,
>incl. sources?
As far as I can tell, the sources in the last version of the package
aren’t even used to build it, because the “source” package ships the
binaries for m68k-bare plus the source o
Hi John,
On Sun, May 31, 2015 at 12:42 AM, John Voltz wrote:
> With the latest sid, is it possible to run X windows (Xorg) yet? I'm
Yes, X is supposed to work.
As you have a Retina Z3, the plain X server for fbdev should work.
The support for Amiga bitplanes may not be included in the Debian pac
With the latest sid, is it possible to run X windows (Xorg) yet? I'm
building amiga-lilo right now, so hopefully I won't have to go through
the early-startup to boot Debian anymore. Also, nobody ever said if the
source code is available for amiboot or where to find it. Google comes
up with nothi
Thorsten,
This is awesome! You guys really rock!
Thanks
Bob
On Sat, 5/30/15, Thorsten Glaser wrote:
Subject: Re: M68K status
To: "John Voltz"
Cc: debian-68k@lists.debian.org
Date: Saturday, May 30, 2015, 4:13 PM
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Ingo Jürgensmann dixit:
>> Sarge, but amiboot 5.6 and 6.0 both have problems. If I try to start
Weren’t most amiboot problems related to…
>Do you have your kernel unzipped?
… this?
>Do you have "devtmpfs.mount=1“ to your options of the kernel co
On 05/28/2015 12:56 AM, John Voltz wrote:
> I just find it interesting that the kernels all seem to hang at the same
> point whenever I start them from the Workbench. I think I tried the
> latest one from the wiki page over the weekend and it did the same
> thing. I would like to figure out why, so
On Thu, May 28, 2015 at 12:56 AM, John Voltz wrote:
> Can you quickly explain how to install amiga-lilo?
There seems to be Debian packages for it, but it may not be in the main archive:
https://people.debian.org/~cts/debian-m68k/amiga-lilo/
This is not the latest version, so it may fail on '060
Hi Adrian,
Out of curiosity: Why aren't you installing an up-to-date Debian
unstable on your Amiga?
I don't see any point trying to debug issues which might have already
beem fixed years ago.
I mean, kernel 2.4.x is almost historic these days and both Sarge and
Etch are just way too old to
Hi John!
Out of curiosity: Why aren't you installing an up-to-date Debian unstable on
your Amiga?
I don't see any point trying to debug issues which might have already beem
fixed years ago.
I mean, kernel 2.4.x is almost historic these days and both Sarge and Etch are
just way too old to star
Hello again,
I let Debian Sarge complete it's install last night on my A3000 (it took
hours) and now today I'm trying to debug my startup issues. See my
attachment with the boot logs. If the attachment doesn't make it through
the mailer I will resend as inline text. I will try the latest kerne
Hi John,
On Wed, May 27, 2015 at 7:25 AM, Ingo Jürgensmann
wrote:
>> I'm just trying to figure out where the status of the m68k port of Debian
>> stands. There doesn't appear to be too much activity on the mailing list,
>> and I see nothing big has made it's
On 05/27/2015 08:38 AM, Finn Thain wrote:
> Some up-to-date information can be found in the wiki.
> https://wiki.debian.org/M68k/Installing
Sprucing this up a bit and making it more up-to-date has been on my
TODO list for quite some time. I am planning to make a guide with
screenshots and all thes
On Tue, 26 May 2015, John Voltz wrote:
> I'm just trying to figure out where the status of the m68k port of
> Debian stands. There doesn't appear to be too much activity on the
> mailing list, and I see nothing big has made it's way to the official
> releases. Can
Am 27.05.2015 um 02:33 schrieb John Voltz :
> I'm just trying to figure out where the status of the m68k port of Debian
> stands. There doesn't appear to be too much activity on the mailing list, and
> I see nothing big has made it's way to the official releases. Can
Hello everyone,
I'm just trying to figure out where the status of the m68k port of
Debian stands. There doesn't appear to be too much activity on the
mailing list, and I see nothing big has made it's way to the official
releases. Can someone update me on where everythin
Tuomas,
You guessed right about memory failing me - it wasn't about DMA in
the end (for some reason, I seem to have DMA stuck in my mind at the
moment), Do you see any other avenues to try and enable tagged
commands in the ESP chip? We tried one config register only so far...
I think I've t
On 09.08.2014 01:25, Michael Schmitz wrote:
Hi Tuomas,
There's still the Amiga Zorro ESP patch out in limbo - DaveM
suggested a change to enable SCSI-2 features to help with extended
message bytes but that did not work as intended. Haven't had time to
follow that one up. Tuomas' fix to the d
Hi Christian,
Last time I had a chance to try this on a non-broken EtherNAT, it
was fine (two years ago IIRC). Need to ask Christian again to test
the current one.
Ask me again when the summer is over. Last I tried I had troubles to power
on the Falcon. Plus I had problems transfering the
Hi Tuomas,
There's still the Amiga Zorro ESP patch out in limbo - DaveM
suggested a change to enable SCSI-2 features to help with extended
message bytes but that did not work as intended. Haven't had time to
follow that one up. Tuomas' fix to the driver to bypass DMA for
message in works OK
On 08.08.2014 11:38, Michael Schmitz wrote:
There's still the Amiga Zorro ESP patch out in limbo - DaveM suggested
a change to enable SCSI-2 features to help with extended message bytes
but that did not work as intended. Haven't had time to follow that one
up. Tuomas' fix to the driver to byp
On 08.08.2014 11:58, Michael Schmitz wrote:
Hi Ingo,
Am 05.08.2014 um 21:40 schrieb Geert Uytterhoeven
:
m68k v3.16 is out!
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
m68k-queue is getting smaller, but there are still a few commits left:
Hmm, what about the Blizzard
On Fri, Aug 08, 2014 at 08:38:28PM +1200, Michael Schmitz wrote:
> Last time I had a chance to try this on a non-broken EtherNAT, it
> was fine (two years ago IIRC). Need to ask Christian again to test
> the current one.
Ask me again when the summer is over. Last I tried I had troubles to power
on
Hi Ingo,
Am 05.08.2014 um 21:40 schrieb Geert Uytterhoeven :
m68k v3.16 is out!
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
m68k-queue is getting smaller, but there are still a few commits left:
Hmm, what about the Blizzard 2060 SCSI driver from Michael & Tuomas
Hi Geert,
m68k v3.16 is out!
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
m68k-queue is getting smaller, but there are still a few commits left:
$ git cherry -v for-3.17 m68k-queue v3.16
- 7e87ff970f7116e46025f226b5aa47bd19e1229b zorro: Use ARRAY_SIZE
- 8e1bf8df8b6db30f2e7
On 08/06/2014 09:35 AM, Geert Uytterhoeven wrote:
>> Add to that the X-Surf100 driver that Michael Karcher wrote [1] but
>> unfortunately he hasn't cleaned up the code yet and submitted it for
>> inclusion in the mainline kernel.
>
> "May I remind you that patches touching areas outside arch/m68k
On Tue, Aug 5, 2014 at 10:29 PM, John Paul Adrian Glaubitz
wrote:
> On Tue, Aug 05, 2014 at 09:52:58PM +0200, Ingo Jürgensmann wrote:
>> Am 05.08.2014 um 21:40 schrieb Geert Uytterhoeven :
>>
>> > m68k v3.16 is out!
>> > git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
>> > m68k-
On Tue, Aug 05, 2014 at 09:52:58PM +0200, Ingo Jürgensmann wrote:
> Am 05.08.2014 um 21:40 schrieb Geert Uytterhoeven :
>
> > m68k v3.16 is out!
> > git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
> > m68k-queue is getting smaller, but there are still a few commits left:
>
> Hm
1 - 100 of 572 matches
Mail list logo
