| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
SVN-Revision: 21269
|
| |
|
|
| |
SVN-Revision: 21265
|
| |
|
|
| |
SVN-Revision: 21145
|
| |
|
|
|
|
| |
and device ids (credits: Bernhard Loos)
SVN-Revision: 21119
|
| |
|
|
|
|
| |
RT-210W, RT-220W and alike boards (closes #6789)
SVN-Revision: 21108
|
| |
|
|
| |
SVN-Revision: 20996
|
| |
|
|
| |
SVN-Revision: 20924
|
| |
|
|
|
|
|
| |
Disable some calls the WRT54G3G implementation does not like
and enable interrupts to allow hotplugging.
SVN-Revision: 20240
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The defined offset is wrong and the fixup-code overrides it
later on so that it never gets used for most PCI devices.
Unfortunately the yenta-socket allocates its own resources
and crashes because of the wrong mem_offset.
It seems that the offset and fixup code came from 2.4 where
resource allocation was handled differently.
This patch removes the unneeded parts and thus enables
the yenta_socket on the WRT54G3G platform.
It was tested on Asus WL500G-Premium (v1 and v2), Linksys
WRT54G3G, Netgear WGT634U
Signed-off-by: Michael Buesch <mb@bu3sch.de>
SVN-Revision: 20239
|
| |
|
|
|
|
|
|
|
|
| |
The patch commited in r18413 was wrong.
This patch prevents prom_init_mem from scanning over 128MB ram.
This is from #6765 and #3177
Refresh all patches
SVN-Revision: 20072
|
|
|
Thanks to acoul and tripolar
SVN-Revision: 19955
|
