This list is closed, nobody may subscribe to it.
2004 |
Jan
(103) |
Feb
(56) |
Mar
(25) |
Apr
(38) |
May
(24) |
Jun
(20) |
Jul
(22) |
Aug
(23) |
Sep
(1) |
Oct
(24) |
Nov
(8) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(14) |
Feb
(23) |
Mar
(7) |
Apr
(23) |
May
(11) |
Jun
(1) |
Jul
(29) |
Aug
(7) |
Sep
|
Oct
|
Nov
(8) |
Dec
(11) |
2006 |
Jan
|
Feb
(24) |
Mar
(22) |
Apr
(1) |
May
(8) |
Jun
|
Jul
|
Aug
(1) |
Sep
(6) |
Oct
|
Nov
(2) |
Dec
(4) |
2007 |
Jan
(1) |
Feb
(4) |
Mar
(5) |
Apr
(10) |
May
|
Jun
(5) |
Jul
(3) |
Aug
(3) |
Sep
(6) |
Oct
(11) |
Nov
(3) |
Dec
(4) |
2008 |
Jan
(8) |
Feb
(19) |
Mar
(43) |
Apr
(27) |
May
(15) |
Jun
(10) |
Jul
(39) |
Aug
(9) |
Sep
(12) |
Oct
(15) |
Nov
(14) |
Dec
(4) |
2009 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(15) |
2010 |
Jan
(2) |
Feb
(7) |
Mar
|
Apr
(16) |
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
|
Oct
(9) |
Nov
(2) |
Dec
|
2011 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(5) |
Dec
(3) |
2012 |
Jan
(12) |
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2017 |
Jan
(1) |
Feb
(2) |
Mar
(7) |
Apr
(2) |
May
|
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Erik T. <rud...@ho...> - 2009-05-01 19:36:09
|
Maybe this answers your question: http://forum.wiibrew.org/read.php?9,40 Date: Fri, 1 May 2009 23:37:03 +0800 From: nig...@gm... To: gc-...@li... Subject: [Gc-linux-devel] about WII build-in wifi driver hello everyone: could anyone tell me the detail why build-in wifi driver does not works fine, my ndsl ds-linux's build-in wifi works fine.. waiting for your reply. nightsuns _________________________________________________________________ Haal meer uit je leven met Windows Live http://www.microsoft.com/netherlands/windowslive/Views/index.aspx |
From: 朱旭伟 <nig...@gm...> - 2009-05-01 15:37:13
|
hello everyone: could anyone tell me the detail why build-in wifi driver does not works fine, my ndsl ds-linux's build-in wifi works fine.. waiting for your reply. nightsuns |
From: Erik T. <rud...@ho...> - 2009-04-30 09:17:09
|
First of all, thanks for the documentation on the gc-linux wiki. It helped me a lot. I've tried compiling the wii-linux kernel with the usb2.0 'patch' as on http://wiibrew.org/wiki/CIOS_usb2 and installed cIOS 36 rev 10. But both Bluetooth and USB stopped working. (Fatal errors regarding the drivers) Later on, I also installed cIOS 202 and somehow Bluetooth was detected during boot. But I was unable to boot into X with Bliight. Switched to whiite today and my keyboard (1.1) is still working, my (2.0) ethernetadapter isn't. Any ideas? |
From: Albert H. <alb...@ya...> - 2009-04-26 10:12:22
|
> just want to know if usb 2.0 is supported in wii-linux > kernel 2.6.29? No, USB 2.0 is currently not supported. It may be supported in the future. Cheers, Albert |
From: chen s. <che...@gm...> - 2009-04-25 02:27:23
|
hi gurus, just want to know if usb 2.0 is supported in wii-linux kernel 2.6.29? here is my usbtree output, i only see the root_hub 12M, is it USB 1.1? /: Bus 01.Port 1: Dev 1, Class=root_hub, Drv=/15p, 12M |_ Port 1: Dev 2, If 0, Prod=BCM2045A, Class=unk., Drv=btusb, 12M |_ Port 1: Dev 2, If 1, Prod=, Class=unk., Drv=btusb, 12M |_ Port 1: Dev 2, If 2, Prod=, Class=vend., Drv=none, 12M |_ Port 1: Dev 2, If 3, Prod=, Class=app., Drv=none, 12M |_ Port 2: Dev 3, If 0, Prod=AX88772, Class=vend., Drv=asix, 12M |_ Port 3: Dev 4, If 0, Prod=USB2.0-CRW, Class=stor., Drv=usb-storage, 12M Thanks, Leo |
From: Maarten t. H. <ma...@tr...> - 2008-12-30 13:51:49
|
On Tuesday 30 December 2008, Christian Grimm wrote: > Is there any way to enable the USB2.0 speed? or will there ever be > support for USB2.0 speed? USB 2.0 requires a different controller type: EHCI instead of OHCI. There is an IOS device node for EHCI: http://www.wiibrew.org/wiki//dev/usb/ehc The wiki says "This doesn't seem to be implemented in retail Wiis."; I don't know if that means that the hardware is not there or the support from IOS is not there. In the latter case, there is a possibility but it would require writing either a new driver in the IOS or replacing the IOS altogether; not an easy task. Bye, Maarten |
From: Christian G. <chr...@li...> - 2008-12-30 12:53:05
|
Dear GameCube / Wii Linux Developers I just installed the latest release of whiite on my Nintendo Wii. It really works great but I have a question about the USB driver (rvl- sthcd). I noticed there is only support for USB 1.1 (see /proc/usb/usb/devices below) devices which prevents my plan for using the Wii as my home server (as I want to connect an external USB2.0 disk). Is there any way to enable the USB2.0 speed? or will there ever be support for USB2.0 speed? Thanks for your answer & keep on rockin' :-) Christian ------------------------- wii:/proc/bus/usb# cat devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh=15 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 2.06 S: Manufacturer=Linux 2.6.27b-isobel-wii rvl-sthcd S: Product=Nintendo Wii USB Host Controller S: SerialNumber=rvl-sthcd C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=057e ProdID=0305 Rev= 1.00 S: Manufacturer=Broadcom Corp S: Product=BCM2045A C:* #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=84(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=04(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms I:* If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none) T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0b95 ProdID=7720 Rev= 0.01 S: Manufacturer=ASIX Elec. Corp. S: Product=AX88772 S: SerialNumber=000001 C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=250mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=asix E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=160ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0781 ProdID=5151 Rev= 0.10 S: Manufacturer=SanDisk Corporation S: Product=Cruzer Micro S: SerialNumber=20060876721B84208617 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb- storage E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms wii:/proc/bus/usb# cat devices |grep spd wii:/proc/bus/usb# cat devices |grep Spd T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh=15 T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#= 4 Spd=12 MxCh= 0 wii:/proc/bus/usb# cat devices |grep Ver D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS= 8 #Cfgs= 1 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 wii:/proc/bus/usb# wii:/proc/bus/usb# cat devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh=15 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0001 Rev= 2.06 S: Manufacturer=Linux 2.6.27b-isobel-wii rvl-sthcd S: Product=Nintendo Wii USB Host Controller S: SerialNumber=rvl-sthcd C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=057e ProdID=0305 Rev= 1.00 S: Manufacturer=Broadcom Corp S: Product=BCM2045A C:* #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=btusb E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=84(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=04(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms I:* If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none) T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0b95 ProdID=7720 Rev= 0.01 S: Manufacturer=ASIX Elec. Corp. S: Product=AX88772 S: SerialNumber=000001 C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=250mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=asix E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=160ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=03 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0781 ProdID=5151 Rev= 0.10 S: Manufacturer=SanDisk Corporation S: Product=Cruzer Micro S: SerialNumber=20060876721B84208617 C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb- storage E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms |
From: Albert H. <alb...@ya...> - 2008-12-04 21:22:30
|
CITEC-PostMaster <mulysatest <at> gmail.com> writes: > 1. I noticed there are many distribution of Linux on Wii. I wondering that gamecube-linux is the same as whiite-linux or not? whiite-linux is a simple Debian 4.0 (etch) based Linux distribution for the Nintendo Wii. The GameCube Linux project is an effort to port the Linux kernel and related userspace tools to the Nintendo GameCube and Wii videoconsoles. > 2. What is the difference between whiite-linux and wii-linux (http://wiibrew.org/wiki/Wii_Linux) Wii Linux (or wii-linux or whatever) is a generic term to designate all Linux distributions running on the Nintendo Wii. All Wii Linux in the end use the kernel that The GameCube Linux (gc-linux) project provides. > 3. Why nativate wireless device doesn't support? Is there any chance it will be supported in the future? It _may_ be supported in the future. > 4. Any win32 software able to achieve the same result as linux console to patitioning the SD card? If no any, does SD card will be detected if I install Linux on VMWare ? I don't know anything about win32 tools nor if a SD card can be used from one of the VMware products. But you can use a live Linux distro CD/DVD (like Ubuntu) to boot you computer into Linux without installing anything on your harddrive, and then proceed to install whiite-linux as per the available instructions. Cheers, Albert |
From: CITEC-PostMaster <mul...@gm...> - 2008-11-30 17:34:40
|
1. I noticed there are many distribution of Linux on Wii. I wondering that gamecube-linux is the same as whiite-linux or not? 2. What is the difference between whiite-linux and wii-linux ( http://wiibrew.org/wiki/Wii_Linux) 3. Why nativate wireless device doesn't support? Is there any chance it will be supported in the future? I planed to install linux on Wii and install VLC then use as multimedia server. Since I already got wireless connection in my house, so my multimedia server would get more benefit from wireless than wired connection. 4. Any win32 software able to achieve the same result as linux console to patitioning the SD card? If no any, does SD card will be detected if I install Linux on VMWare ? |
From: Mike <ms...@ms...> - 2008-09-22 15:06:58
|
Thanks... I got a login now... but I don't know what to write there. I can't find the new site for GCLIB, or even a backup mirror. Is it discontinued? If it had a free software license, then we could put up a most recent version. >> http://www.gc-linux.org/wiki/FAQ >> * The external link to "GCLIB" is broken > > ... > > It's a wiki, press the edit button. |
From: Malcolm <mal...@gm...> - 2008-09-22 09:22:40
|
2008/9/21 Mike <ms...@ms...> > http://www.gc-linux.org/wiki/FAQ > * The external link to "GCLIB" is broken ... It's a wiki, press the edit button. -- Malcolm Parsons |
From: Mike <ms...@ms...> - 2008-09-21 20:34:02
|
I sent the info below to gc-...@li..., and got no response. Is the gc-linux-docs list dead? Also, there's lots of spam on news://news.gmane.org/gmane.linux.ports.game-cube.devel Is it possible to clean that up? ------------------------------------------------------------------------ http://www.gc-linux.org/wiki/FAQ * The external link to "GCLIB" is broken http://www.gc-linux.org/wiki/How_to_develop_for_GameCube_Linux * "Mod That Cube" link broken http://www.gc-linux.org/wiki/Getting_Started * "PSUL". No page/description on what PSUL is? |
From: Malcolm <mal...@gm...> - 2008-07-20 15:15:36
|
On my widescreen LCD TV, there are 19 pixel black borders on either side when using wii linux. This patch gets rid of them. It's another hack, ideally fbset would let you adjust the left and right margins. patch also includes previous vertical overscan changes. -- Malcolm Parsons |
From: Malcolm <mal...@gm...> - 2008-07-12 21:46:02
|
2008/7/12 Maarten ter Huurne <ma...@tr...>: > On Saturday 12 July 2008, Malcolm wrote: >> 3) Write a driver that can send and receive UDP packets using IOS >> sockets. Implement IP over UDP using TUN/TAP in a similar way to IP over >> DNS. http://thomer.com/howtos/nstx.html > A combination of TUN and exposing IOS sockets to user space would allow all > three options: Sounds like a plan. > How does the demo sending work? Does the Wii act like an access point to the > DS? Or are the Wii and the DS just two normal hosts connected to a normal > access point? The Wii sends beacons, so it's acting like an access point to the DS. No other access point is used. DS demo downloading isn't a standard protocol. > The device nodes "/dev/net/ip/bottom" and "/dev/wl0" haven't been reverse > engineered yet (at least, no public documentation seems to be available), > maybe one of these allow lower level access? That's what I'm hoping. > Patching the IOS to add ioctls that allow you to send and receive raw IP > packets would be sufficient. Still not an easy task, but not as hard as > replacing IOS entirely. I think IP packets is still too high level, ethernet packets are what we want to send. I'm not keen on patching/replacing IOS. > Possibly another option: > > 7) Use ptrace() from an external process to intercept socket system calls > from a process and perform IOS socket calls instead. > - Not a transparent solution > + Works with existing binaries Using a library and LD_PRELOAD could work too. -- Malcolm Parsons |
From: Maarten t. H. <ma...@tr...> - 2008-07-12 21:18:58
|
On Saturday 12 July 2008, Malcolm wrote: > 1) Use IOS sockets to implement a network driver > - How? > > 2) Use IOS sockets from userspace > - Only works with modified programs > > 3) Write a driver that can send and receive UDP packets using IOS > sockets. Implement IP over UDP using TUN/TAP in a similar way to IP over > DNS. http://thomer.com/howtos/nstx.html > - Requires another computer on the network to act as a proxy > + Could work A combination of TUN and exposing IOS sockets to user space would allow all three options: 1) Figure out from the IP packets what socket calls the Linux program was making and replay that using the IOS sockets. 2) Ignore TUN and only use the IOS sockets. 3) Traffic from the TUN device is tunneled over IOS sockets. Also, debugging is a lot easier in user space, so even if option 1 in kernel space is your long-term goal, implementing it in user space first is probably a good idea. > 4) Hope that the IOS interface for sending DS demos is low level > enough to do normal wifi. > - Requires reverse engineering work > - May not be possible How does the demo sending work? Does the Wii act like an access point to the DS? Or are the Wii and the DS just two normal hosts connected to a normal access point? The device nodes "/dev/net/ip/bottom" and "/dev/wl0" haven't been reverse engineered yet (at least, no public documentation seems to be available), maybe one of these allow lower level access? > 5) Replace IOS > - Requires lots of reverse engineering work > - Risky Patching the IOS to add ioctls that allow you to send and receive raw IP packets would be sufficient. Still not an easy task, but not as hard as replacing IOS entirely. > 6) Give up and use a USB wifi adaptor It would be a shame to ignore the hardware that every Wii has built in. Possibly another option: 7) Use ptrace() from an external process to intercept socket system calls from a process and perform IOS socket calls instead. - Not a transparent solution + Works with existing binaries Bye, Maarten |
From: <pcw...@uc...> - 2008-07-12 19:56:50
|
>2) Use IOS sockets from userspace >- Only works with modified programs That's not necessarily true: a userspace TUN program could be used to provide a standard Unix interface for programs, while keeping around the option to use IOS sockets at a lower level for programs that want to. I would think this is the best option myself... Patrick |
From: Malcolm <mal...@gm...> - 2008-07-12 18:31:09
|
1) Use IOS sockets to implement a network driver - How? 2) Use IOS sockets from userspace - Only works with modified programs 3) Write a driver that can send and receive UDP packets using IOS sockets. Implement IP over UDP using TUN/TAP in a similar way to IP over DNS. http://thomer.com/howtos/nstx.html - Requires another computer on the network to act as a proxy + Could work 4) Hope that the IOS interface for sending DS demos is low level enough to do normal wifi. - Requires reverse engineering work - May not be possible 5) Replace IOS - Requires lots of reverse engineering work - Risky 6) Give up and use a USB wifi adaptor -- Malcolm Parsons |
From: Groepaz <gr...@gm...> - 2008-07-12 15:13:18
|
On Samstag 12 Juli 2008, Malcolm wrote: > 1) Write directly to EFB, use GX to copy to XFB > + No CPU overhead > - Max yres of 528 > - Max xres of 640 > - No ypan or ywrap > > 2) Write to RAM, use CPU to copy to XFB > - Large CPU overhead > + Max yres of 574 > + Max xres of 720 > + ypan or ywrap > > 3) Write to RAM, use CPU copy to EFB, use GX to copy to XFB > - small CPU overhead > - Max yres of 528 > - Max xres of 640 > + ypan or ywrap > > 4) Write to RAM, use CPU to create texture, use GX to draw texture to > EFB and copy to XFB > - some CPU overhead > - Max yres of 528 > - Max xres of 640 > + ypan or ywrap you forgot one important thing ... all ways except the first require an additional video buffer in main ram, and thus waste memory. -- http://www.hitmen-console.org http://www.pokefinder.org http://ftp.pokefinder.org The Scene always wins. |
From: Malcolm <mal...@gm...> - 2008-07-12 15:04:19
|
1) Write directly to EFB, use GX to copy to XFB + No CPU overhead - Max yres of 528 - Max xres of 640 - No ypan or ywrap 2) Write to RAM, use CPU to copy to XFB - Large CPU overhead + Max yres of 574 + Max xres of 720 + ypan or ywrap 3) Write to RAM, use CPU copy to EFB, use GX to copy to XFB - small CPU overhead - Max yres of 528 - Max xres of 640 + ypan or ywrap 4) Write to RAM, use CPU to create texture, use GX to draw texture to EFB and copy to XFB - some CPU overhead - Max yres of 528 - Max xres of 640 + ypan or ywrap CPU overhead could be reduced for mostly static images using deferred IO. http://lwn.net/Articles/259210/ -- Malcolm Parsons |
From: Matthias S. <mat...@go...> - 2008-07-12 14:48:02
|
That's great! Same here, i always had to switch to 16:9 on my 4:3 TV to see the last line. Thanks! 2008/7/12 Malcolm <mal...@gm...>: > I can't see the top and bottom lines of text on the framebuffer in wii > linux on my TV. > > This patch adjusts the y resolution of the framebuffer so that all > lines are visible. > > It's a hack, but it does make it easier to type commands. > -- > Malcolm Parsons > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Gc-linux-devel mailing list > Gc-...@li... > https://lists.sourceforge.net/lists/listinfo/gc-linux-devel > > |
From: Malcolm <mal...@gm...> - 2008-07-12 14:42:33
|
I can't see the top and bottom lines of text on the framebuffer in wii linux on my TV. This patch adjusts the y resolution of the framebuffer so that all lines are visible. It's a hack, but it does make it easier to type commands. -- Malcolm Parsons |
From: Albert H. <alb...@gm...> - 2008-03-28 17:01:55
|
Malcolm <malcolm.parsons <at> gmail.com> writes: > > On 27/03/2008, Albert Herranz <herraa1 <at> users.sourceforge.net> wrote: > > > - s/DVD/Disk/ on gcn-di.c. > > The second D in DVD stands for Disc, not Disk. > > http://en.wikipedia.org/wiki/DVD > > http://docs.info.apple.com/article.html?artnum=302152 > That "disk" comes from "disk interface" not the second D in DVD. http://www.google.com/patents?id=Rk0NAAAAEBAJ&dq=6609977 Cheers, Albert |
From: Malcolm <mal...@gm...> - 2008-03-28 13:40:06
|
On 27/03/2008, Albert Herranz <he...@us...> wrote: > - s/DVD/Disk/ on gcn-di.c. The second D in DVD stands for Disc, not Disk. http://en.wikipedia.org/wiki/DVD http://docs.info.apple.com/article.html?artnum=302152 -- Malcolm Parsons |
From: Daniel T. <da...@re...> - 2008-03-24 17:24:55
|
On Sun, 2008-03-23 at 13:59 -0400, Andrew Kohlsmith (lists) wrote: > Is there a better (cleaner) way of developing against CVS HEAD aside from > copying the tree on top of a clean kernel? I've always run a for each on the checkout (something like the following): <untested_code> cd checked_out_directory for i in `find . ! -type d` do diff -Nau ../linux/$i $i done > gc-linux.patch </untested_code> I've then manage apply the patch to the pristine tree with quilt. This is quite a good working model if you don't have CVS write access since you just keep the master patch at the bottom of the stack and add you own changes as seperate patches higher up the stack (ready to be posted to the list). I assume the 'real' developers may have a more sophisticated approach that makes CVS commits easy as well. -- Daniel Thompson <da...@re...> |
From: Andrew K. (lists) <ak...@mi...> - 2008-03-23 18:01:15
|
I've pulled CVS HEAD and applied (cp -a) it to a clean 2.6.24 tree, but it seems that starlet.h was not committed. Is this intentional? Is there a better (cleaner) way of developing against CVS HEAD aside from copying the tree on top of a clean kernel? Regards, Andrew |