[Bug 15573] New: add hotplug support for marvell discovery gigabit ethernet driver.
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Fri Sep 16 09:28:07 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=15573
Ubuntu | linux
Summary: add hotplug support for marvell discovery gigabit
ethernet driver.
Product: Ubuntu
Version: unspecified
Platform: powerpc
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: linux
AssignedTo: ben.collins at ubuntu.com
ReportedBy: luther at debian.org
QAContact: kernel-bugs at lists.ubuntu.com
CC: cjwatson at ubuntu.com
As ubuntu moved away from using discover in favour of pure hotplug (or
derivative), the pegasos gigabit ethernet driver, mv643xx_eth, was no more
loaded automatically, which was problematic with u-i, and broke some other
stuff, like trying to use nfsroot over the gigabit ethernet port and other such
application that need the network interface.
This patch :
http://svn.debian.org/wsvn/kernel/dists/sid/linux-2.6/debian/patches-debian/powerpc-mv643xx-hotplug-support.patch?op=file&rev=0&sc=0
Scheduled for addition in the next round of debian kernels, adds the mv643xx_eth
module to the pci subsystem, in the same way that we used to map the discovery
II northbridge pci id in the discover method, and thus adds an hotplug event for
this device.
This is not an ideal solution, since we should instead create a builtin or
plateform kind of bus, where those devices reside, and add propper hotplug
events to all such devices, mostly used in the embedded world, but this is
probably something for after the ppc64/ppc reorganisation.
In any case, this code only affects hardware possessing a marvell discovery II
northbridge, and there is only the pegasos in the kind of market ubuntu supports
that uses it (others are probably routers and other such appliances).
Friendly,
Sven Luther
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-bugs
mailing list