coreboot May 2004

coreboot@coreboot.org

35 participants
149 discussions

Config.lb language
by Mathieu Deschamps 18 May '04

18 May '04

Hello, I'am looking for a while to set a new options in Config.lb to test my V2 VGABIOS code : i need VGABIOS_START options and ZKERNEL START also, theses are deprecated in V2. Is the config python script openned to user's new entries ? I've read in Stefan Reinauer's AMD 64 port guide in Command definitions section from Language that he declares option A=(1+2) or option B=0xa. Why not... but in this case wouldn't the script complains while using a undeclared option ? Further in, if declared it'll complained it is a unexistant option ... so how could I add my option entry in the config dictionnary without making any DIY fixup nor breaking rules of use ? BTW i know this question may be senstive (but sensible:) couldn't it be possible that the config.py dictionnary be external and no longer err.. BTW where is it holds exactly ?!? I mean to be able to see in a external file (i let external to config.py) commands and codes it triggers (commands and available options). Then this file could be parse by config.py. IHMO, add a options would be far easier :) mathieu.

3 2

Re: bios documentation
by Ken Fuchs 18 May '04

18 May '04

Peter Karlsson wrote: >Is there an English version of this >(http://www.qsl.net/f6flv/docbios.html)? Here's what http://translate.google.com offers: http://translate.google.com/translate?hl=en&sl=fr&u=http://www.qsl.net/f6fl… I don't think it's a very good translation, but it's better than nothing, perhaps? Other free machine translation web servers may a do better job. Sincerely, Ken Fuchs <kfuchs(a)winternet.com>

2 1

Getting Started with freebios2!
by Jay Miller 18 May '04

18 May '04

Disclaimer: I too am a N00B and these are my observations thus far. They may not be 100% correct, but these things have worked for me. I hope that they'll help other N00Bz get started. WHAT IS FREEBIOS2? Well I stumbled upon freebios2 when I couldn't find support in the freebios tree for my Tyan s2885. Then I noticed under the CVSWeb browser for the project the freebios2 directory. Apparently, this is what will be LinuxBIOS V2. They've done away with kernel patches, so you don't need to worry about patching the kernel like in V1. Instead there is an intermediary payload that can be Etherboot, FILO, or some other loader to get your Linux kernel into memory. WHY CAN'T I GET THE SOURCES FROM SOURCEFORGE (ANYMORE)? If you're like me, all of a sudden CVS access stopped working. Well, they changed the BIND implementation, so the documentation is out of date. You need to use, "cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/freebios login". There is still no password for anonymous login. WHERE DO I START? Build the documentation under freebios2/documentation. It will give you a solid overview of how the project works, including how to download the source you just downloaded. ;-) Freebios2 supports a number of newer boards. Tyan are particularly well-supported and the EPIA boards are actively being worked on. Look under, "freebios2/targets..." for the collection. HOW DO I BUILD FREEBIOS2? Once you've selected a vendor and mainboard you should execute, "./buildtarget <vendor>/<board>". This will generate all sources specific to your mainboard. To make a rom image, start your make in the freebios2/targets/<vendor>/<board>/<board> directory. If all goes smoothly you should get a linuxbios.rom image. HOW DO I FLASH A ROM? There are a number of methods and I'm not versed enough to cover them all. But I have successfully used the BIOS flash utility from AMI, and I currently use a professional Data I/O burner. I spent a lot of time trying to figure out the proper format to use on my burner. There is no format; it's just a straight binary image, so use binary mode (on the Data I/O it's "absolute binary (16)"). There is also a flash-n-burn utility in the source tree. Perhaps someone on the list can add the specifics of how to get that going on this thread. HOW DO I CHANGE CONFIGURATION OF MY IMAGE? First take a look at freebios2/targets/<vendor>/<board>/Config.lb. This is the main configuration file for your ROM image. This is where you specify what payload to use, and most of the settings that anyone would care about. Make sure to do a "./buildtarget <vendor>/<board>" whenever you modify this file. However, in my case I was running into issues running my dual-processor board with only one processor. As it turns out there is another Config.lb located in freebios2/src/mainboard/<vendor>/<board>. This file controls the contents of some of the generated sources for your board. To date, this is the only way I was able to prevent my ROM image from trying to initialize a CPU that wasn't there. WHY DON'T I SEE ANYTHING HAPPENING? In most cases the VGA support just isn't there yet. So go find yourself a null modem cable and hook up your console at 15200-8-N-1, and sit back and watch the fireworks! WHAT ABOUT PAYLOADS? I'm currently exploring this area. The first payload I used successfully was FILO. No you don't make pastry with it. It is a bootloader that acts much like LILO. You can get the source here: http://felixx.tsn.or.jp/~ts1/filo. If you have an IDE disk with a Linux kernel on it, this is the way to get started. If you're diskless then you may want to try Etherboot: http://etherboot.sourceforge.net. This payload gives you the ability to load over the network, but requires you to configure a DHCP server and TFTP server at a minimum. Like LinuxBIOS, Etherboot expects an ELF formatted image, so if you're loading a kernel across the network you need to run it through mkelfImage. As of now the correct version to use is 2.5. You can get the latest sources here: ftp://ftp.lnxi.com/pub/mkelfImage/mkelfImage-2.5.tar.gz. WHAT ABOUT ZELF? This is my latest N00B stumbling block, and unfortunately I haven't found an answer. I know that it's a compressed elf format, but I can't figure out what I need to do to get elfboot (part of LinuxBIOS) to load payloads with the ZELF extension. So for now I would recommend N00Bz stick with ELF format, until we get a definitive answer. Hope this is helpful, good luck! Jay Miller Actuality Systems, Inc. jmiller(a)acutality-systems.com

1 0

Re: bios documentation
by Peter Karlsson 17 May '04

17 May '04

--- Mathieu Deschamps <mdeschamps(a)mangrove-systems.com> wrote: >Hello, > >Here's what i've found for low level programmers :] >It's a doc on PCAT BIOS, detailling every interruptions >and their values .This is just fine a trusted adress >but it's all in french. >If you're looking for these type of infos >go and have a look : http://www.qsl.net/f6flv Is there an english version of this (http://www.qsl.net/f6flv/docbios.html)? Best regards Peter Karlsson _____________________________________________________________ Gratis e-postadress ---> http://www.mailamig.nu

2 1

Epia-MII VGA not working and PCMCIA rebooting
by Ignacio Verona 17 May '04

17 May '04

Hi! Linuxbios is working prety well now on my Epia mII 10k, but a few problems: 1. I can't get VGA to work. I've extracted it from a original-bios booted system with dd if=/proc/kcore of=video.bios.bin bs=1 count=65536 skip=790528 and then appended it to my filo payload like the HOWTO says I've to do, and modified the config file with all the options in EPIA howto, but nothing shows up on my monitor (tft screen, has it something to do with?) 2. If I boot up my mobo without the PCMCIA/CF module on, it boots properly but, if I put it on and try to boot, linux bios does somethings and then reboot, forever. any known bug about this? thanks!

4 9

Re: Epia-MII VGA not working and PCMCIA rebooting
by Dave Ashley 17 May '04

17 May '04

> b8? Anybody know what that one is? The vgabios itself has a bug in it. The b8 is an invalid INT # and what has happened is the vgabios code itself has crashed and is executing randomly. On the EPIA-M I had seen this problem on certain units where if the motherboard got too hot (but not really that hot) and you reboot, it would just sit there beeping forever with its onboard noisemaker. This was with the stock AWARD bios. The problem would go away if I set up a fan to blow on the motherboard and cool it down. Under linuxbios the problem would manifest itself where during the vgabios init code you'd get into an endless loop of invalid INT callbacks. So it would stop the system from booting. My "fix" was to only allow certain INT's in the callback and so if an invalid one happens, we just abort out of the VGA init code. This worked fine for our purposes, the vgabios had been able to init the hardware enough to get the system working, and life could go on. Note also when this endless INT callback thingy happened in linuxbios, if I blasted the fan on the motherboard to cool it down, that would fix the problem. I really don't know how a bug in the vgabios could manifest itself only on certain motherboards and only when they get hot. But it's not impossible. Note these int21 handler code was required for getting the vgabios working on the EPIA-M. Whether the thing is a case statement or a table is irrelevant, the case statement approach allows for endless customization. The point is the int21 callbacks must be implemented. That's how a black box like the vgabios can be delivered to VIA without source, yet VIA can integrate it into their AWARD bios. The INT 21 callbacks like 4F01 are for the vgabios to query the system to find out how much video ram has been reserved for the display (I default to 8M), what is the preferred output device, and other mysterious and poorly documented settings. The documentation I was going on was the CLE266 BIOS PORTING GUIDE from VIA, an NDA document. It is cryptic and incomplete (typical). It doesn't cover all of the INT21 callbacks that the vgabios makes use of. Even if you boot off the AWARD bios, then run the vgabios with the emulator and make use of the AWARD bios to know what to return for these 4fxx INT21 callbacks, you're still left with the bug in the vgabios itself. I'm satisfied there is a bug there so I haven't spent any more time trying to improve the situation. Long story short I don't know why Ignacio Verona's not getting VGA output on his EPIA-MII. However there is a reason for all the business in linuxbios with the unsupport int printing + aborting the vgabios execution and the code in the epia-m tree that handles the callbacks, so don't start thinking about ripping it out unless you really know what you're doing. -Dave

2 1

Re: Epia-MII VGA not working ...
by Ignacio Verona 17 May '04

17 May '04

Ron: Thanks for your answ. Reading the serial output can you say something about the PCMCIA problem? And what about tft? May be cause VGA no to work? Right now I do not have any CRTs here... Mathieu: Yes, I'm on v1 right now. And about the combined filo+vgabios payload this is what I do for creating: dd if=filo.elf of=vga+filo.bin bs=1 seek=65536 And using vga+filo.bin as my payload linuxbios still boot up to the kernel, but VGA does not come up. Maybe could I go to V2 for beeing exactly on the same point as you? I could give it a try this tonight. Also: Do you know if acpi is working on V2? I've plans to "try" (only try, I don't know if I've the required programming skills) to implement it on v1, but if it's working on v2 I could skip this step and do all the job on VGA. Thanks! > Hi > > It seems i am on the same point as you. This project is simply > fascinating, and so much time consuming :) > > I've done this famous dd with the kcore and so on, but i think to do > miss something. > I've got a classic crt screen but nothing appear either. Also I'am > working with v2 . my Linuxbios is booting to the kernel so this is ok. > > What is not, is that VGABIOS on V2 LB is not fully operationnal, i want > to make it be. Please could you tell me how you did "append it to my > filo payload like the HOWTO says and modified the config file" as ? > It could geratly help me in trying to make a port to V2 since i've > understood you are in V1, don't you ? > > Though the details of your experiments could unstuck me. > > > Le dim 16/05/2004 Ã 21:47, Ignacio Verona a Ã©crit : >> Hi! Linuxbios is working prety well now on my Epia mII 10k, but a few >> problems: >> >> 1. I can't get VGA to work. I've extracted it from a original-bios >> booted >> system with >> dd if=/proc/kcore of=video.bios.bin bs=1 count=65536 skip=790528 >> and then appended it to my filo payload like the HOWTO says I've to do, >> and modified the config file with all the options in EPIA howto, but >> nothing shows up on my monitor (tft screen, has it something to do >> with?) >> >> 2. If I boot up my mobo without the PCMCIA/CF module on, it boots >> properly >> but, if I put it on and try to boot, linux bios does somethings and then >> reboot, forever. any known bug about this? >> >> thanks! >> >> _______________________________________________ >> Linuxbios mailing list >> Linuxbios(a)clustermatic.org >> http://www.clustermatic.org/mailman/listinfo/linuxbios >> >

3 3

bios documentation
by Mathieu Deschamps 17 May '04

17 May '04

Hello, Here's what i've found for low level programmers :] It's a doc on PCAT BIOS, detailling every interruptions and their values .This is just fine a trusted adress but it's all in french. If you're looking for these type of infos go and have a look : http://www.qsl.net/f6flv mathieu.

1 0

答复: USB boot
by YhLu 17 May '04

17 May '04

Not yet. Status: 1. UHCI support: bulk transfer not working. 2. OHCI support: need add code to support ED and TD this week. Regards YH -----邮件原件----- 发件人: Jay Miller [mailto:jmiller@actuality-systems.com] 发送时间: 2004年5月17日 8:36 收件人: YhLu 抄送: linuxbios(a)clustermatic.org; pyro(a)linuxlabs.com 主题: Re: USB boot Has the code for USB support been committed, and if so, where? Thanks, Jay Miller Actuality Systems, Inc. jmiller(a)acutality-systems.com

1 0

Re: USB boot
by YhLu 17 May '04

17 May '04

Let me know if your testbed is ready, and I would send my last usb dir tar ball to you. Regards YH -----邮件原件----- 发件人: Steven James [mailto:pyro@linuxlabs.com] 发送时间: 2004年5月17日 6:14 收件人: YhLu 抄送: Linuxbios; Takeshi Sone 主题: Re: USB boot Greetings, Sorry about the delay in replying. The length field is encoded as n-1 with 0x7ff a special value meaning 0. IIRC, a USB protocol error would cause a stall condition. A 0 transfer when data is expected is a SCSI level error. As you can see, the USB code doesn't have nearly enough error checking. It looks like control messages are fine since the device gets configured, but the bulk transfers seem to be broken. It might be good to write poison to the buffers to verify that no data goes to them. Since everything seems to be returning no data, probably the SCSI command is not being sent to the device correctly. Hopefully, this week, I can get my test board going again so I can do some debugging as well. G'day, sjames -------------------------steven james, director of research, linux labs ... ........ ..... .... 230 peachtree st nw ste 2701 the original linux labs atlanta.ga.us 30303 -since 1995 http://www.linuxlabs.com office & fax 866.545.6306 ----------------------------------------------------------------------- On Fri, 14 May 2004, YhLu wrote: > Here are the new results. > > 1. for usb_control_msg: every return + 2047 packet???? > 2. for bulk_transfer: every out is ok, but every in only return fixed 2048 > len data. > > Regards > > YH > > Loading Etherboot version: 5.2.4 > ROM segment 0x0000 length 0x0000 reloc 0x00020000 > CPU 2285 Mhz > Etherboot 5.2.4 (GPL) http://etherboot.org Tagged ELF for [TG3][FILO] > Relocating _text from: [0002d5f0,0008fc20) to [efe9d9d0,eff00000) > Probing pci nic... > [tg3-5704]Ethernet addr: 00:E0:81:61:8C:27 > Tigon3 [partno(BCM95704A6) rev 2003 PHY(5401)] (PCIX:100MHz:64-bit) > <abort> > Probing pci nic... > [tg3-5704]Ethernet addr: 00:E0:81:61:8C:28 > Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit) > <abort> > Probing pci nic... > Probing pci disk... > [FILO]FILO version 0.4.1 (root@tst2723-rh9) Fri May 14 17:10:13 PDT 2004 > Press <Enter> for default boot, or <Esc> for boot prompt... > boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf > LinuxLabs USB bootloader > raw frame_list is at 00079560 > frame_list is at 00079630 > frame_list_link: addr: 00078570 > frame_list_link: raw addr: efef5f40 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 00070500 > raw frame_list is at 0007b560 > frame_list is at 0007b630 > frame_list_link: addr: 00078590 > frame_list_link: raw addr: efef5f60 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 00070540 > raw frame_list is at 0007d560 > frame_list is at 0007d630 > frame_list_link: addr: 000785b0 > frame_list_link: raw addr: efef5f80 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 00070580 > raw frame_list is at 0007f560 > frame_list is at 0007f630 > frame_list_link: addr: 000785d0 > frame_list_link: raw addr: efef5fa0 > frame_list_link: terminate: 00000000 > frame_list_link: queue: 00000001 > frame_list_link: depth: 00000000 > dummy_td = 000705c0 > Found OHCI at 0d182630 > Resetting OHCI > USB HC reset_hc usb-0d182630: ctrl = 0x00000600 ;ohc_init setting framelist > to: efef7000 > Starting OHCI > Found OHCI at 0d183630 > Resetting OHCI > USB HC reset_hc usb-0d183630: ctrl = 0x00000600 ;ohc_init setting framelist > to: efef9000 > Starting OHCI > Found UHCI at 00002400 > Resetting UHCI > uhc_init setting framelist to: efefb000 > Starting UHCI > HCI at 00002400 > Found UHCI at 00002420 > Resetting UHCI > uhc_init setting framelist to: efefd000 > Starting UHCI > HCI at 00002420 > poll_usb1 i=0 poll_usb1 i=1 poll_usb1 i=2 poll_u_root_hub1 v=00000480 > poll_u_root_hub1 v=00001493poll_u_root_hub2 v=00001493 poll_u_root_hub21 > v=00001493 Connection on port 00002412 > New USB device, setting address 00000003 > usb_control_msg: request_type = 00000000 request = 00000005 wLength=0 > usb_control_message returning 2047 > Fetching device descriptor length > usb_control_msg: request_type = 00000080 request = 00000006 wLength=8 > usb_control_message returning 2054 > Fetching device descriptor > usb_control_msg: request_type = 00000080 request = 00000006 wLength=18 > usb_control_message returning 2064 > Fetching config descriptor length > usb_control_msg: request_type = 00000080 request = 00000006 wLength=8 > usb_control_message returning 2054 > Fetching config descriptor > usb_control_msg: request_type = 00000080 request = 00000006 wLength=32 > usb_control_message returning 2078 > device: > bLength: 00000012 > type: 00000001 > bcdVersion: 0000000200000000 > Class: 00000000 > SubClass: 00000000 > protocol: 00000000 > max_packet: 00000040 > idVendor: 00001005 > idProduct: 0000b113 > bcdDeviceVersion: 0000000100000000 > iManufacturor: 00000000 > iProduct: 00000001 > iSerial: 00000002 > bNumConfig: 00000001 > config: > bLength: 00000009 > type: 00000002 > wTotalLength: 00000020 > bNumInterfaces: 00000001 > bConfigurationValue: 00000001 > iConfiguration: 00000000 > bmAttributes: 00000080 > bMaxPower: 000000fa > > Interface(00081e6b): > bLength: 00000009 > type: 00000004 > bInterfaceNumber: 00000000 > bAlternateSetting: 00000000 > bNumEndpoints: 00000002 > bInterfaceClass: 00000008 > bInterfaceSubClass: 00000006 > bInterfaceProtocol: 00000050 > iInterface: 00000000 > > Endpoint (00081e74): > bLength: 00000007 > type: 00000005 > bEndpointAddress: 00000081 > bmAttributes: 00000002 > wMaxPacketSize: 00000040 > bInterval: 00000000 > > Endpoint (00081e7b): > bLength: 00000007 > type: 00000005 > bEndpointAddress: 00000002 > bmAttributes: 00000002 > wMaxPacketSize: 00000040 > bInterval: 00000000 > Selecting Configuration number 00000001: > usb_control_msg: request_type = 00000000 request = 00000009 wLength=0 > usb_control_message returning 2047 > clear stall on ep=00000081 > usb_control_msg: request_type = 00000002 request = 00000001 wLength=0 > usb_control_message returning 2047 > clear stall on ep=00000002 > usb_control_msg: request_type = 00000002 request = 00000001 wLength=0 > usb_control_message returning 2047 > 00000008:00000006:00000050 > Manufacturor: unknown > usb_control_msg: request_type = 00000080 request = 00000006 wLength=4 > usb_control_message returning 2050 > usb_control_msg: request_type = 00000080 request = 00000006 wLength=32 > usb_control_message returning 2078 > Product: USB Flash Drive > usb_control_msg: request_type = 00000080 request = 00000006 wLength=4 > usb_control_message returning 2050 > usb_control_msg: request_type = 00000080 request = 00000006 wLength=32 > usb_control_message returning 2078 > Serial: 070B01001340CA0 > desc address (phy) = efeff820, (virt) = 00081e50 > conf address (phy) = efeff832, (virt) = 00081e62 > Mass storage, bulk only SCSI transparent > Requesting initial sense data > bulk_transfer: ep = 00000002 len=31 > bulk_transfer returning 31 > bulk_transfer: ep = 00000081 len=32 > bulk_transfer returning 2048 > bulk_transfer: ep = 00000081 len=13 > bulk_transfer returning 2048 > sense data > :00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000 > 00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000 > 0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00 > 000000:00000000:00000000:00000000:00000000:00000000:00000000 > > code = 00000000 key = 00000000 > > Info: 00000000 > bulk_transfer: ep = 00000002 len=31 > bulk_transfer returning 31 > scsi_command reading 8 bytes > bulk_transfer: ep = 00000081 len=8 > bulk_transfer returning 2048 > scsi_command read 2048 bytes > scsi_command fetching csw > bulk_transfer: ep = 00000081 len=13 > bulk_transfer returning 2048 > scsi_command csw is 2048 bytes > 1 0 byte blocks > part address (phy) = efeff400, (virt) = 00081a30 > bulk_transfer: ep = 00000002 len=31 > bulk_transfer returning 31 > scsi_command reading 512 bytes > bulk_transfer: ep = 00000081 len=512 > bulk_transfer returning 2048 > scsi_command read 2048 bytes > scsi_command fetching csw > bulk_transfer: ep = 00000081 len=13 > bulk_transfer returning 2048 > scsi_command csw is 2048 bytes > ll_read_block returns 512 > 0: boot=00000000, start=00000000 length=00000000 > 1: boot=00000000, start=00000000 length=00000000 > 2: boot=00000000, start=00000000 length=00000000 > 3: boot=00000000, start=00000000 length=00000000 > DEVICE CONFIGURED > poll_usb1 i=3 poll_u_root_hub1 v=00000480 poll_u_root_hub1 v=00000480 > poll_usb1 i=0 poll_usb1 i=1poll_usb1 i=2 poll_u_root_hub1 v=00000480 > poll_u_root_hub1 v=00000495 poll_usb1 i=3 poll_u_root_hub1 v=00000480 > poll_u_root_hub1 v=00000480 Found USB block device 3 > Requesting initial sense data > bulk_transfer: ep = 00000002 len=31 > bulk_transfer returning 31 > bulk_transfer: ep = 00000081 len=32 > bulk_transfer returning 2048 > bulk_transfer: ep = 00000081 len=13 > bulk_transfer returning 2048 > sense data > :00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:000 > 00000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:0000000 > 0:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00 > 000000:00000000:00000000:00000000:00000000:00000000:00000000 > > code = 00000000 key = 00000000 > > Info: 00000000 > bulk_transfer: ep = 00000002 len=31 > bulk_transfer returning 31 > scsi_command reading 512 bytes > bulk_transfer: ep = 00000081 len=512 > bulk_transfer returning 2048 > scsi_command read 2048 bytes > scsi_command fetching csw > bulk_transfer: ep = 00000081 len=13 > bulk_transfer returning 2048 > scsi_command csw is 2048 bytes > ll_read_block returns 512 > part address (phy) = efeffa94, (virt) = 000820c4 > 0: boot=00000000, start=00000000 length=00000000 > 1: boot=00000000, start=00000000 length=00000000 > 2: boot=00000000, start=00000000 length=00000000 > 3: boot=00000000, start=00000000 length=00000000 > sector= 0 bulk_transfer: ep = 00000002 len=31 > bulk_transfer returning 31 > scsi_command reading 512 bytes > bulk_transfer: ep = 00000081 len=512 > bulk_transfer returning 2048 > scsi_command read 2048 bytes > scsi_command fetching csw > bulk_transfer: ep = 00000081 len=13 > bulk_transfer returning 2048 > scsi_command csw is 2048 bytes > sector= 68 bulk_transfer: ep = 00000002 len=31 > bulk_transfer returning 31 > scsi_command reading 512 bytes > bulk_transfer: ep = 00000081 len=512 > bulk_transfer returning 2048 > scsi_command read 2048 bytes > scsi_command fetching csw > bulk_transfer: ep = 00000081 len=13 > bulk_transfer returning 2048 > scsi_command csw is 2048 bytes >

1 0

← Newer
1
2
3
4
5
6
7
8
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot May 2004