Kernel 4.8

[xeno74]

Hi All,

Here is the alpha3 for testing.

New:

• KVM updates
• DRM updates (DRM 2.46.0)
• PowerPC updates
• BTRFS support improved (Thanks to Srtest)
• Xorg and Radeon 32-bit bug fixed (Thanks to Michael Ellerman)
• Fix coherent_dma_mask for dma engine (Thanks to Darren Stevens)
• New Nemo patch 4.8-3
• Phoronix articles, reviews and news stories covering Linux 4.8
• Linux Git log

Issue: Internal CompactFlash (CF) card device is not recognized

Download: vmlinux-4.8-alpha3-AmigaONE_X1000.tar.gz

Cheers,

Christian

[xeno74]

FYI: PowerPC-4.8-2 merge integrated in the Linux Git source code today

[Srtest]

FYI: PowerPC-4.8-2 merge integrated in the Linux Git source code today

I have a question regarding the PC vs AmigaLinux world: if something like this is done on a pc it is most likely to fail to boot and the installation gets destroyed (like switching on ahci or something). When you change a lot of settings at the core like those Power changes can it have a dramatic effect on a Linux installation?

[xeno74]

FYI: PowerPC-4.8-2 merge integrated in the Linux Git source code today

I have a question regarding the PC vs AmigaLinux world: If something like this is done on a pc it is most likely to fail to boot and the installation gets destroyed (like switching on ahci or something). When you change a lot of settings at the core like those Power changes can it have a dramatic effect on a Linux installation?

It could be. Therefore we have to test it.

By the way, I have found some information about the electra IDE CF card device: http://linuxppc-dev.ozlabs.narkive.com/ ... tform-glue

I checked the kernel config and the merge but without any success.

[Srtest]

"It could be. Therefore we have to test it."

Well then, there should be this giant warning about it which I guess some will act upon. I meen that's the way they do things in Linux I guess such as when they updated Systemd and because I learned stuff this past year I was able to chroot my way out of a reinstallation. Maybe the regular user won't go to such lengths and I don't think it is a must. Testers implies testers, nothing more.

Edit: let me simplify that - If I test something in my mind I take a chance of not being able to boot, I don't take a chance of not being able to boot again with a previous version or not being able to boot via downgrading a bad package on the user level.

[xeno74]

"It could be. Therefore we have to test it."

Well then, there should be this giant warning about it which I guess some will act upon. I mean that's the way they do things in Linux I guess such as when they updated Systemd and because I learned stuff this past year I was able to chroot my way out of a reinstallation. Maybe the regular user won't go to such lengths and I don't think it is a must. Testers implies testers, nothing more.

Yes, you're right. Have you already tested your Btrfs volume with the alpha3?

@All

It seems there is a problem with the PA Semi PWRficient Gigabit Ethernet. It tries very often to connect to the network but there isn't a network cable plugged in. There are two new commits about our PA Semi PWRficient Gigabit Ethernet in the Git source code.

• 2016-07-15 net: ethernet: pasemi_mac: use phy_ethtool_{get|set}_link_ksettings
• 2016-07-15 net: ethernet: pasemi_mac: use phydev from struct net_device

PLEASE test the PA Semi PWRficient Gigabit Ethernet with the alpha3.

[Srtest]

Yes, you're right. Have you already tested your Btrfs volume with the alpha3?

I need to first locate a disk-on-key that actually still works because a lack of a controller makes almost all of them crap

[xeno74]

Edit: let me simplify that - If I test something in my mind I take a chance of not being able to boot, I don't take a chance of not being able to boot again with a previous version or not being able to boot via downgrading a bad package on the user level.

I see! OK.

[mechanic]

Tested on Deb-stretch.

My PAsemi Eth is cooked so cannot test that.
CFcard is not seen, but SB600 PATA HD works fine.
Sound is strange(?) works fine in some apps, not at all in others.
Screensaver works.
I'm using LXDE. LXQT works but has some issues yet to be worked out.
Youtube works fine in SMTube, not in QUPzilla. QUPzilla works fine with 4.1.29.

There are some other oddities but it's early yet.

[xeno74]

Tested on Deb-stretch.

My PAsemi Eth is cooked so cannot test that.
CFcard is not seen, but SB600 PATA HD works fine.
Sound is strange(?) works fine in some apps, not at all in others.
Screensaver works.
I'm using LXDE. LXQT works but has some issues yet to be worked out.
Youtube works fine in SMTube, not in QUPzilla. QUPzilla works fine with 4.1.29.

There are some other oddities but it's early yet.

Hi Mechanic,

Thanks a lot for testing the alpha3.

@All

FYI:

Hello Nicholas

On 06/08/2016, Nicholas Piggin wrote:
> Hi Christian,
[...]
> As for your driver support, it would indeed be a good idea to
> get it supported in the upstream kernel. You should post a
> new mail about that. Take a look at these 3 commits:
>
> 61f7162117d4767875825abf2f6ed1eeebbcceed
> 9cd55be4d22376893d2818ce3c0e5706a3d74121
> ca99140a63b7326ee9a38f64c326317f2c63b594
>
> Your patch comes from code based on the second one. The last
> commit removed it, and says that it is not the best way to
> implement it. You could cc this list and some of the people
> involved with those commits and ask ask for advice about
> getting your driver supported.

Actually, it's almost supported by the base PASemi code anyway, there is a
PCMCIA driver in setup.c, but our hardware has been changed enough to make it
hang the system when used. I should probably take another look and see If I
can fix that. The other option would be to move the above patch to where we
add our rtc platform device. One thing that does confuse me is the interrupt,
it's attached to GPIO 0, so should be on the mpic int 0 (or maybe 16?)but I
could never get it to work.

Regards
Darren

Cheers,

Christian