| kets as much as possible.
Zerocopy output packets are basically undone by netfilter becuase all of
it assumed it was working with linear socket buffers.
Rusty is fixing this piece by piece. He is nearly done with this work.
PRI1
power management
~~~~~~~~~~~~~~~~
(Pat) There is some preliminary work at bk://ldm.bkbits.net/linux-2.5-power,
though I''''m currently in the process of reworking it.
It includes:
o New device power management core code, both for individual devices,
and for global state transitions.
PRI1
o A generic user interface for triggering system power state transitions.
PRI1
o Arch-independent code for performing state transitions, that calls
platform-specific methods along the way.
PRI1
o A better suspend-to-disk mechanism than swsusp.
There are various other details to be worked out, which are the real fun
part. And of course, driver support, but that is something that can happen
at any time.
(Alan)
PRI2
o Frame buffer restore codepaths (that requires some deep PCI magic)
PRI2
o XFree86 hooks
PRI2
o AGP restoration
PRI2
o DRI restoration
(davej/Alan: not super-critical, can crash laptop on restore. davej
looking into it.)
PRI2
o IDE suspend/resume without races (Ben is looking at this a little)
PRI2
o Pat: There are already CPU device structures; MTRRs should be a
dynamically registered interface of CPUs, which implies there needs
to be some other glue to know that there are MTRRs that need to be
saved/restored.
PRI1
global
~~~~~~
o 64-bit dev_t. Seems almost ready, but it''''s not really known how much
work is still to do. Patches exist in -mm but with the recent rise of the
neo-viro I''''m not sure where things are at.
PRI1
o We need a kernel side API for reporting error events to userspace (could
be async to 2.6 itself)
(Prototype core based on netlink exists)
PRI2
o Kai: Introduce a sane, easy and standard way to build external modules
PRI2
o Kai: Allow separate src/objdir
PRI2
o general confusion over firmware policy:
o do we mandate that it be uploaded from userspace?
o Is binary-blob-in-kernel-image OK?
o Each driver (wireless, scsi, etc) seems to do it in a different,
private manner.
gregkh: patch exists, drivers can be ported to use new infrastructure at
any time.
PRI1
o larger cpumask_t - supporting more than BITS_PER_LONG CPUs.
wli: patch exists. ia32, ppc are done. ppc64 in progress. Needs work
for other architectures.
PRI1
o pavel: ioctl32 emulation should be shared across architectures. (patch
exists).
PRI2
drivers
~~~~~~~
o Alan: Cardbus/PCMCIA requires all Russell''''s stuff is merged to do
multiheader right and so on
PRI1
drivers/acpi/
~~~~~~~~~~~~~
o alan: VIA APIC stuff is one bit of this, there are also some other
reports that were caused by ACPI not setting level v edge trigger some
times
PRI1
o mochel: it seems the acpi irq routing code could use a serious rewrite.
grover: The problem is the ACPI irq routing code is trying to piggyback
on the existing MPS-specific data structures, and it''''s generally a hack.
So yes mochel is right, but it is also purging MPS-ities from common code
as well. I''''ve done some preliminary work in this area and it doesn''''t seem
to break anything (yet) but a rewrite in this area imho should not be
rushed out the door. And, I think the above bugs can be fixed w/o the
rewrite.
PRI2
o mochel: ACPI suspend doesn''''t work. Important, not cricital. Pat is
working it.
PRI2
drivers/block/
~~~~~~~~~~~~~~
o Floppy is almost unusably buggy still
akpm: we need more people to test & report.
alan: "Floppy has worked for me since the patches that went in 2.5.69-ac
and I think -bk somewhere"
PRI1
drivers/char/
~~~~~~~~~~~~~
o Alan: Multiple serious bugs in the DRI drivers (most now with patches
thankfully). "The badness I know about is almost entirely IRQ mishandling.
DRI failing to mask PCI irqs on exit paths."
(This is understood and fixed in DRI CVS)
PRI1
o Various suspect things in AGP.
PRI1
drivers/ide/
~~~~~~~~~~~~
(Alan)
o IDE requires bio walking
"Bartlomiej has IDE multisector working" (does that mean it''''s fixed?)
PRI1
o IDE PIO has occasional unexplained PIO disk eating reports
PRI1
o IDE has multiple zillions of races/hangs in 2.5 still
PRI1
o IDE scsi needs rewriting
PRI2
o IDE needs significant reworking to handle Simplex right
PRI2
o IDE hotplug handling for 2.5 is completely broken still
PRI2
o There are lots of other IDE bugs that wont go away until the taskfile
stuff is included, the locking bugs that allow any user to hang the IDE
layer in 2.5, and some other updates are forward ported. (esp. HPT372N).
PRI1
drivers/isdn/
~~~~~~~~~~~~~
(Kai, rmk)
o isdn_tty locking is completely broken (cli() and friends)
PRI2
o fix lots of remaining bugs in the isdn link layer / hisax protocol layer
/ hisax subdrivers, so that at least 99% of the users have a usable ISDN
subsystem
PRI1
o fix other drivers
PRI2
o lots more cleanups, adaption to recent APIs etc
PRI3
o fixup tty-based ISDN drivers which provide TIOCM* ioctls (see my recent
3-set patch for serial stuff)
Alternatively, we could re-introduce the fallback to driver ioctl parsing
for these if not enough drivers get updated.
PRI3
drivers/net/
~~~~~~~~~~~~
o davej: Either Wireless network drivers or PCMCIA broke somewhen. A
configuration that worked fine under 2.4 doesn''''t receive any packets. Need
to look into this more to make sure I don''''t have any misconfiguration that
just ''''happened to work'''' under 2.4
PRI1
drivers/scsi/
~~~~~~~~~~~~~
o qlogic follies:
- jejb: Merge the feral driver. It covers all qlogic chips: 1020 all
the way up to 23xxx. mjacob is promising a "major" rewrite which
eliminates this as a candidate for immediate inclusion. Panics on my
parisc hardware, works on my ia64. BK tree is
http://linux-scsi.bkbits.net/scsi-isp-2.5
- qla2xxx: only for FC chips. Has significant build issues. hch
promises to send me a "must fix" list for this. I plan not to merge this
until I at least see how Qlogic responds to the issues. Can''''t currently
build this for my only fibre card (a qla2100). BK tree is at
http://linux-scsi.bkbits.net/scsi-qla2xxx-2.5
- I think the best plan currently is not to merge either of these, but
keep shadow BK trees for them (thus holding out the possibility of
merger) to see how they evolve. I agree with hch that feral seems to be
in the better shape but, barring directions to the contrary, I can''''t see
why both shouldn''''t be included eventually.
PRI2
arch/i386/
~~~~~~~~~~
o Also PC9800 merge needs finishing to the point we want for 2.6 (not all).
PRI3
o ES7000 wants merging (now we are all happy with it). That shouldn''''t be a
big problem.
PRI2
o davej: PAT support (for mtrr exhaustion w/ AGP)
PRI2
o 2.5.x won''''t boot on some 440GX
alan: Problem understood now, feasible fix in 2.4/2.4-ac. (440GX has two
IRQ routers, we use the $PIR table with the PIIX, but the 440GX doesnt use
the PIIX for its IRQ routing). Fall back to BIOS for 440GX works and Intel
concurs.
PRI1
o 2.5.x doesn''''t handle VIA APIC right yet.
1. We must write the PCI_INTERRUPT_LINE
2. We have quirk handlers that seem to trash it.
PRI1
o ACPI needs the relax patches merging to work on lots of laptops
alan: ACPI relax stuff is in 2.4-ac, compaq workaround is in next -ac
coming. These seem to deliver the goods - toshibas now work a treat. Some
other relax bits are being discussed (assume local0 starts 0 etc) and
progress looks great. This can occur before 2.6 or during.
PRI1
o ECC driver questions are not yet sorted (DaveJ is working on this) (Dan
Hollis)
alan: ECC - I have some test bi 上一页 [1] [2] [3] [4] [5] [6] [7] [8] [9] 下一页 | 
