Thread: (no subject)
Brought to you by:
aeb,
bencollins
From: Karthikeyan M. <kma...@ho...> - 2001-01-29 17:14:16
|
Hi, I've been consistently running into this problem while trying to capture DV: after a few frames (20 seconds or so), dvgrab hangs. I see a message in /var/log/message saying ohci1394_0: waking up dma cxt 2, processing is probably too slow. I tried increasing the iso buffer to 16MB, with no improvement. I tried compiling the drivers with 1394_VERBOSE_DEBUG on. The problem goes away, but I see a lot of frames dropped and buffer underrun messages from dvgrab. I tried compiling without VERBOSE_DEBUG, and changed the DBGMSG in insert_dma_buffer to always print a message. This time, the problem appears later (after 3 minutes or so). In the meanwhile, I still see occasional "waking up dma cxt 2" messages interspersed with normal dma insertion messages. The messages in /var/log/messages stop all of a sudden, and dvgrab hangs. Any idea what could be happening? BTW, I've been able to successfully burn a CD using a Que CD writer using the same 1394 setup and the sbp2_1394 drivers (thats raw mode, I guess, so if it's a driver problem I'm seeing, It's probably limited to iso mode) I'm using pcmcia-cs, kernel 2.4.0 the patched 1394 drivers for 2.4.0 on a Vaio F-250 with a pyro DV for notebooks adapter. Karthik _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. |
From: Gregory A. H. <gha...@my...> - 2002-06-08 16:11:24
|
I'm using the NewMotion enclosure with an HP9900j DVD/CD-RW drive. I haven= 't tried it on Linux yet, but it works just dandy on windoze. I'm wondering if your NewMotion enclosure was properly recognizing the driv= e you=20 are using - I think the NewMotion enclosures configure their config rom bas= ed on=20 what you have installed into them. Make sure your drive is set to master, = etc. so=20 that the bridge card can see what your device is. As to what you are experiencing with your TI based device, I wish I could h= elp, but I have no experience with that one. Greg On Friday, June 07, 2002 3:45 PM, Stefan Richter [SMTP:richtest@bauwesen.tu= -cottbus.de] wrote: > On 8 Jun, Paul Moore wrote: > > I confirmed from the supplier who looked at the circuit > > board of the Dvico MomoBay FX-1A that the chip is a > > TSB42AA9A, not the TS42AA9A as stated in the benchmark test. > >=20 > > TI Has information about this at: > > http://focus.ti.com/docs/prod/productfolder.jhtml?genericPartNumber=3DT= SB42AA9A > [...] > >>Does anyone have any experience with this chipset, whether it > >>does or does not work with the latest ieee1394 tarball? >=20 > I have a MomoBay CX-1 with the predecessor TSB42AA9 and it works > fine for me and ieee1394-471 (don't read a recommendation for > -471 here). This doesn't guarantee anything about the TSB42AA9A > but at least http://focus.ti.com/docs/prod/folders/print/tsb42aa9.html > and http://focus.ti.com/docs/prod/folders/print/tsb42aa9a.html > reveal no significant difference at first glance. >=20 > >>After no luck with the NewMotion/Oxford 911(OXFW911) drive > >>enclosures due to: > >> > >>** ieee1394: Node 01:1023 has non-standard ROM format (0 quads), cannot= parse > >>** ieee1394: sbp2: Error logging into SBP-2 device - login timed-out > >>** ieee1394: sbp2: sbp2_login_device failed >=20 > I think other people use 911-based drive bays quite happily. > --=20 > Stefan Richter > -=3D=3D=3D=3D=3D-=3D--=3D- -=3D=3D- --=3D=3D=3D > http://arcgraph.de/sr/ >=20 > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux1394-user ---------------------------------------------------------- Gregory A. Havenga Tekton Software Engineering Services mailto:gha...@my... - http://www.tektonusa.com ---------------------------------------------------------- |
From: Gregory H. <gre...@en...> - 2002-10-17 02:25:44
|
From: Marco B. <be...@ma...> - 2002-10-29 22:33:46
|
Hello, I apologize in advance for my newbieness. I have a Dazzle(tm) card that converts analog video to digital and viceversa; it is a breakout box connected to the computer through two cables. one is a ieee1394 and the other is something else (through which the device receives the power line). It looks like an extended serial connector with more pins (but smaller than a parallel). It came with a Dell dimension 8200 and I think it is a OEM product because it looks different from anything from the Dazzle website. Needless to say, it works under XP home, but I'd like it in Mandrake 9. I'd need some direction from more experienced users to sort this out. Thank you for your help Hereafter is all information I deem pertinent rpm -qa | grep 1394 libraw1394_5-0.9.0-1mdk libavc1394_0-0.4.1-1mdk lsmod Module Size Used by Tainted: P loop 11376 0 (autoclean) sg 31276 0 (autoclean) isofs 25652 1 (autoclean) inflate_fs 17892 0 (autoclean) [isofs] udf 85472 0 (autoclean) raw1394 7004 0 sr_mod 15096 2 (autoclean) floppy 49340 0 (autoclean) parport_pc 21672 1 (autoclean) lp 6720 0 (autoclean) parport 23936 1 (autoclean) [parport_pc lp] agpgart 31840 3 (autoclean) NVdriver 1065920 10 (autoclean) snd-seq-midi 3680 0 (autoclean) (unused) snd-emu10k1-synth 4220 0 (autoclean) (unused) snd-emux-synth 25532 0 (autoclean) [snd-emu10k1-synth] snd-seq-midi-emul 4880 0 (autoclean) [snd-emux-synth] snd-seq-virmidi 2888 0 (autoclean) [snd-emux-synth] snd-seq-oss 26176 0 (unused) snd-seq-midi-event 3208 0 [snd-seq-midi snd-seq-virmidi snd-seq-oss] snd-seq 33264 2 [snd-seq-midi snd-emux-synth snd-seq-midi-emul snd-seq-virmidi snd-seq-oss snd-seq-midi-event] snd-pcm-oss 36932 0 snd-mixer-oss 9016 0 [snd-pcm-oss] snd-emu10k1 56592 0 [snd-emu10k1-synth] snd-pcm 55808 0 [snd-pcm-oss snd-emu10k1] snd-timer 9964 0 [snd-seq snd-pcm] snd-util-mem 1280 0 [snd-emux-synth snd-emu10k1] snd-rawmidi 12864 0 [snd-seq-midi snd-seq-virmidi snd-emu10k1] snd-seq-device 3836 0 [snd-seq-midi snd-emu10k1-synth snd-emux-synth snd-seq-oss snd-seq snd-emu10k1 snd-rawmidi] snd-ac97-codec 25508 0 [snd-emu10k1] snd-hwdep 3840 0 [snd-emu10k1] snd 24804 0 [snd-seq-midi snd-emux-synth snd-seq-virmidi snd-seq-oss snd-seq-midi-event snd-seq snd-pcm-oss snd-mixer-oss snd-emu10k1 snd-pcm snd-timer snd-util-mem snd-rawmidi snd-seq-device snd-ac97-codec snd-hwdep] soundcore 3780 0 [snd] nfsd 66576 0 (autoclean) lockd 46480 0 (autoclean) [nfsd] sunrpc 60188 0 (autoclean) [nfsd lockd] ip_vs 74328 0 (autoclean) af_packet 13000 0 (autoclean) 8139too 14472 1 (autoclean) mii 1152 0 (autoclean) [8139too] ohci1394 16812 0 ieee1394 31532 0 [raw1394 ohci1394] nls_cp850 3580 1 (autoclean) vfat 9588 1 (autoclean) fat 31864 0 (autoclean) [vfat] nls_iso8859-1 2844 6 (autoclean) ntfs 72908 1 (autoclean) supermount 14340 2 (autoclean) ide-cd 28712 0 cdrom 26848 0 [sr_mod ide-cd] ide-scsi 8212 1 scsi_mod 90372 3 [sg sr_mod ide-scsi] usb-uhci 21676 0 (unused) usbcore 58304 1 [usb-uhci] rtc 6560 0 (autoclean) I also have kino, gscanbus (I tried dvgrab but it just captures nothing). kino does start but it captures nothing, even when a source is connected to the breakout box (I used an ordinary VCR, same setting that works in windows) gscanbus shows me one icon and clicking it I get SelfID Info ----------- Physical ID: 0 Link active: Yes Gap Count: 63 PHY Speed: S400 PHY Delay: <=144ns IRM Capable: Yes Power Class: None Port 0: Not connected Port 1: Not connected Port 2: Not connected Init. reset: Yes CSR ROM Info ------------ GUID: 0x25F3030000323014 Node Capabilities: 0x000083C0 Vendor ID: 0x00000000 Unit Spec ID: 0x00000000 Unit SW Version: 0x00000000 Model ID: 0x00000000 Nr. Textual Leafes: 1 Vendor: XEROX CORPORATION Textual Leafes: Linux OHCI-1394 AV/C Subunits ------------- N/A Here is lspci: 00:00.0 Host bridge: Intel Corp. 82850 850 (Tehama) Chipset Host Bridge (MCH) (rev 04) 00:01.0 PCI bridge: Intel Corp. 82850 850 (Tehama) Chipset AGP Bridge (rev 04) 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA PCI Bridge (rev 04) 00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 04) 00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 04) 00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 04) 00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 04) 00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 04) 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX420] (rev a3) 02:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C (rev 10) 02:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a) 02:09.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a) 02:0a.0 PCI bridge: Hint Corp HB1-SE33 PCI-PCI Bridge (rev 13) 03:00.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) 03:08.0 Multimedia controller: C-Cube Microsystems E4? (rev b1) |
From: Henry L. <hl...@da...> - 2002-12-03 19:16:19
|
From: Pieter W. <Pieter.Willems@FillFactory.com> - 2003-02-12 10:14:00
|
Hello, =20 I am a complete newbie to the linux 1394 subsystem, and I am just installing the libraw1394 on my mandrake 9.0. The installation went fine, but when I try to test it with gscanbus, I don't seem to be able to compile gscanbus. I always get the error "No targets specified and no makefile found. Stop." Ther eis something in the manual about changing a path, but I'm not sure on what I should change. Any help would be great.... =20 Pieter |
From: James T. <jw...@pa...> - 2003-02-12 10:34:57
|
i am by no means an expert on this topic, in fact i just accessed my two maxtor 1394 drives from a debian 2.4.20 build, but i wonder if you have scsci_mod and/or sbp2 modules installed. here's my lsmod: [...] lsmod Module Size Used by Tainted: P sd_mod 9916 4 (autoclean) vfat 9244 2 (autoclean) fat 28888 0 (autoclean) [vfat] sbp2 15616 2 scsi_mod 50940 2 [sd_mod sbp2] NVdriver 1065184 10 (autoclean) raw1394 6416 0 (unused) ohci1394 15200 0 (unused) ieee1394 28296 0 [sbp2 raw1394 ohci1394] emu10k1 56992 1 ac97_codec 9312 0 [emu10k1] soundcore 3268 4 [emu10k1] i load ieee1394, ohci1394 and raw1394 from /etc/modules, in that order, and then insmod scsi_mod and sbp2 by hand. hth, - james Pieter Willems wrote: > Hello, > > I am a complete newbie to the linux 1394 subsystem, and I am just > installing the libraw1394 on my mandrake 9.0. The installation went > fine, but when I try to test it with gscanbus, I don't seem to be able > to compile gscanbus. I always get the error "No targets specified and > no makefile found. Stop." Ther eis something in the manual about > changing a path, but I'm not sure on what I should change. Any help > would be great.... > > Pieter |
From: Matt A. <mat...@ae...> - 2003-02-12 13:36:30
|
Hello everyone! Well, on my Fujitsu C Series Lifebook I've been unable to get ANY linux distro to work with my 1394 Maxtor hard drive. I get that infamous error about time loging into device. A google search shows many people asking about that, but few, if any, answers that work. On Linux, it seems that you either have hardware that works right off the bat, or your hardware just does not work. Enter FreeBSD 5.0 Release! Firewire drive working PERFECTLY! It has taken me longer to get a working "Desktop" solution. Complete with Java and Flash, Open Office etc. than it does with any linux distro. But I can use my external drive! Yee Haw! Matt Anderson |
From: Andreas M. <and...@iv...> - 2003-02-12 10:53:02
|
On Wed, Feb 12, 2003 at 11:11:19AM +0100, Pieter Willems wrote: > fine, but when I try to test it with gscanbus, I don't seem to be able > to compile gscanbus. I always get the error "No targets specified and no How did you start the compile? Like this? ./configure make -- Andreas Micklei IVISTAR Kommunikationssysteme AG Ehrenbergstr. 19 / 10245 Berlin http://www.ivistar.de |
From: Pieter W. <Pieter.Willems@FillFactory.com> - 2003-02-14 18:00:45
|
Hello, I'm planning on developing an application which will have to send and receive data over the FireWire bus under Linux. I will have to be able to send isochronous packets en send/receive asynchronous packets. Can anyone help me with the source code of some FireWire applications where this kind of communication is performed? I would like to take a look on their approach and look how this is exactly done. Thanks a lot! Pieter |
From: Dan D. <da...@de...> - 2003-02-14 21:56:22
|
Please look at the software on http://www.linux1394.org/links.html On Fri, 2003-02-14 at 12:57, Pieter Willems wrote: > Hello, > > I'm planning on developing an application which will have to send and > receive data over the FireWire bus under Linux. I will have to be able > to send isochronous packets en send/receive asynchronous packets. Can > anyone help me with the source code of some FireWire applications where > this kind of communication is performed? I would like to take a look on > their approach and look how this is exactly done. Thanks a lot! > > Pieter |
From: Pieter W. <Pieter.Willems@FillFactory.com> - 2003-04-02 14:55:02
|
Hello, =20 I'm starting to write a FireWire program under linux. As I am very new to programming under linux in general, I'm starting with a very simple test program. In this program I want to create a handle associated with the firewire device and get the portinfo. The code as i tried it is displayed here: =20 #ifdef HAVE_CONFIG_H #include <config.h> #endif =20 #include <errno.h> #include <string.h> #include <stdlib.h> =20 #include <stdio.h> #include <libraw1394/raw1394.h> //#include <libraw1394/csr.h> =20 int main(int argc, char *argv[]) { //printf("Hello, world!\n"); int numcards; struct raw1394_portinfo pinf[16]; raw1394handle_t handle; handle =3D raw1394_new_handle(); numcards =3D raw1394_get_port_info(handle, pinf, 16); return EXIT_SUCCESS; } =20 I am using KDevelop on a SuSE 8.1 prof. distribution. When I compile this code I get the following compile error: =20 main.o: In function `main':=20 /root/isotraffic/isotraffic/main.c:37: undefined reference to `raw1394_new_handle'=20 /root/isotraffic/isotraffic/main.c:38: undefined reference to `raw1394_get_port_info'=20 collect2: ld returned 1 exit status=20 gmake[3]: *** [isotraffic] Error 1=20 gmake[3]: Leaving directory `/root/isotraffic/isotraffic'=20 gmake[2]: Leaving directory `/root/isotraffic/isotraffic'=20 gmake[2]: *** [all-recursive] Error 1=20 gmake[1]: *** [all-recursive] Error 1=20 gmake[1]: Leaving directory `/root/isotraffic'=20 gmake: *** [all] Error 2=20 *** failed ***=20 =20 It could be that I am doing something very stupid, but hey, can you blame a newbie!? If you need more info to solve this problem just let me know.=20 =20 Thanks in advance! =20 Pieter |
From: Stefan R. <st...@s5...> - 2003-04-02 18:06:16
|
On 2 Apr, Pieter Willems wrote: > I am using KDevelop on a SuSE 8.1 prof. distribution. When I compile > this code I get the following compile error: > > main.o: In function `main': > /root/isotraffic/isotraffic/main.c:37: undefined reference to > `raw1394_new_handle' > /root/isotraffic/isotraffic/main.c:38: undefined reference to > `raw1394_get_port_info' > collect2: ld returned 1 exit status It is actually a linker error, that is, main.c has been compiled successfully but the linking of the object file with libraries did not resolve all functions you use. Look for the place where the libraries to link against are defined in the KDevelop IDE and add libraw1394 (or only the term raw1394, or -lraw1394 ... just as other libraries, I never used KDevelop myself). -- Stefan Richter -=====-=--== -=-- ---=- http://arcgraph.de/sr/ |
From: Pieter W. <Pieter.Willems@FillFactory.com> - 2003-04-16 11:42:02
|
Hello, =20 I am currently trying to write an application that does some address range mapping. This address range mapping succeeds (terurn value 0), but when I try to read from it (using an other pc), I am unable to do so. =20 Here are the packets that are sent/received: =20 ReadBlockReq: destination id:2 transaction label:1 retry code: retry_1 tcode: ReadBlockReq priority: 0 sourceID: 0 destination offset: 0xFFFF00003000 data length: 16 header CRC: 0x344CAE56 =20 ReadBlockResp: DestinationID: 0 transaction label:1 retry code: retry_X tcode: ReadBlockResp priority: 0 sourceID: 2 response code: resp_address_error data length: 0 header CRC: 0x92BD3CC4 =20 =20 This is a piece of code I use to allocate the address range: =20 retval=3Draw1394_arm_register(handle, 0xFFFFF00003000,0x100,initial_value,(unsigned long) &arm_reqhandle,RAW1394_ARM_READ,RAW1394_ARM_READ,0); while (terval!=3D20){ retval=3Draw1394_loop_iterate(handle); } =20 =20 Any ideas of what I'm doing wrong here? =20 Pieter =20 |
From: Manfred W. <we...@ic...> - 2003-04-16 19:35:28
|
Pieter Willems wrote: > I am currently trying to write an application that does some address > range mapping. This address range mapping succeeds (terurn value 0), but > when I try to read from it (using an other pc), I am unable to do so. It seems that you map the adress range from 0xfffff00003000 to 0xfffff000030ff (BTW that address does not exist, the biggest address is 0xffffffffffff) and then read from 0xffff00003000, which is not within that range. Manfred |
From: Pieter W. <Pieter.Willems@FillFactory.com> - 2003-05-06 08:52:07
|
Hello, I would like to make some changes to the config rom for my my FireWire application. I Found that the definition of it is located in the ohci1394.c file in the function ohci_init_config_rom(). I used it to change the textual descriptor of the root directory and the vendor ID. I also added a Module Hw Version with it.=20 But I still have a few problems. -I would like to create a unit directory with 2 leaves. It would have to look a little like this: =09 -- unit directory |_ Unit spec ID =3D myname (0xmyvalue) |_ Unit Sw Version =3D 0xmyvalue I don't realy know how to do this. Do you have any ideas? This is the code of my ohci_init_config_rom() so far: static void ohci_init_config_rom(struct ti_ohci *ohci) { struct config_rom_ptr cr; memset(&cr, 0, sizeof(cr)); memset(ohci->csr_config_rom_cpu, 0, sizeof (ohci->csr_config_rom_cpu)); cr.data =3D ohci->csr_config_rom_cpu; /* Bus info block */ cf_unit_begin(&cr, 0); cf_put_1quad(&cr, reg_read(ohci, OHCI1394_BusID)); cf_put_1quad(&cr, reg_read(ohci, OHCI1394_BusOptions)); cf_put_1quad(&cr, reg_read(ohci, OHCI1394_GUIDHi)); cf_put_1quad(&cr, reg_read(ohci, OHCI1394_GUIDLo)); cf_unit_end(&cr); DBGMSG(ohci->id, "GUID: %08x:%08x", reg_read(ohci, OHCI1394_GUIDHi), reg_read(ohci, OHCI1394_GUIDLo)); /* IEEE P1212 suggests the initial ROM header CRC should only * cover the header itself (and not the entire ROM). Since we do * this, then we can make our bus_info_len the same as the CRC * length. */ ohci->csr_config_rom_cpu[0] |=3D cpu_to_be32( (be32_to_cpu(ohci->csr_config_rom_cpu[0]) & 0x00ff0000) << 8); reg_write(ohci, OHCI1394_ConfigROMhdr, be32_to_cpu(ohci->csr_config_rom_cpu[0])); /* Root directory */ cf_unit_begin(&cr, 1); /* Vendor ID */ cf_put_keyval(&cr, 0x03, 0x00094B); cf_put_refer(&cr, 0x81, 2); /* Textual description unit */ cf_put_keyval(&cr, 0x0c, 0x0083c0); /* Node capabilities */ /* NOTE: Add other unit referers here, and append at bottom */ //cf_put_keyval(&cr, 0x04, 0x991029); //cf_put_keyval(&cr, 0x0A, 0x00094B); cf_put_keyval(&cr, 0x0B, 0x000802); cf_unit_end(&cr); /* Textual description - "Linux 1394" */ cf_unit_begin(&cr, 2); cf_put_keyval(&cr, 0, 0); cf_put_1quad(&cr, 0); cf_put_str(&cr, "FillFactory NV"); cf_unit_end(&cr); ohci->csr_config_rom_length =3D cr.data - ohci->csr_config_rom_cpu; } Thanks already! Pieter |
From: Dan D. <da...@de...> - 2003-05-06 21:33:23
|
See the code in libavc1394 CVS at http://sf.net/projects/libavc1394/ under the librom1394 directory and the accompanying example program. It uses the raw1394 functions to get and set the config ROM image, but it shows adding a unit directory like what you are looking for. On Tue, 2003-05-06 at 04:52, Pieter Willems wrote: > Hello, > > I would like to make some changes to the config rom for my my FireWire > application. I Found that the definition of it is located in the > ohci1394.c file in the function ohci_init_config_rom(). > I used it to change the textual descriptor of the root directory and the > vendor ID. I also added a Module Hw Version with it. > But I still have a few problems. > > -I would like to create a unit directory with 2 leaves. It would > have to look a little like this: > > -- unit directory > |_ Unit spec ID = myname (0xmyvalue) > |_ Unit Sw Version = 0xmyvalue > > I don't realy know how to do this. Do you have any ideas? This is the > code of my ohci_init_config_rom() so far: > > static void ohci_init_config_rom(struct ti_ohci *ohci) > { > struct config_rom_ptr cr; > > memset(&cr, 0, sizeof(cr)); > memset(ohci->csr_config_rom_cpu, 0, sizeof > (ohci->csr_config_rom_cpu)); > > cr.data = ohci->csr_config_rom_cpu; > > /* Bus info block */ > cf_unit_begin(&cr, 0); > cf_put_1quad(&cr, reg_read(ohci, OHCI1394_BusID)); > cf_put_1quad(&cr, reg_read(ohci, OHCI1394_BusOptions)); > cf_put_1quad(&cr, reg_read(ohci, OHCI1394_GUIDHi)); > cf_put_1quad(&cr, reg_read(ohci, OHCI1394_GUIDLo)); > cf_unit_end(&cr); > > DBGMSG(ohci->id, "GUID: %08x:%08x", reg_read(ohci, > OHCI1394_GUIDHi), > reg_read(ohci, OHCI1394_GUIDLo)); > > /* IEEE P1212 suggests the initial ROM header CRC should only > * cover the header itself (and not the entire ROM). Since we do > * this, then we can make our bus_info_len the same as the CRC > * length. */ > ohci->csr_config_rom_cpu[0] |= cpu_to_be32( > (be32_to_cpu(ohci->csr_config_rom_cpu[0]) & 0x00ff0000) > << 8); > reg_write(ohci, OHCI1394_ConfigROMhdr, > be32_to_cpu(ohci->csr_config_rom_cpu[0])); > > /* Root directory */ > cf_unit_begin(&cr, 1); > /* Vendor ID */ > cf_put_keyval(&cr, 0x03, 0x00094B); > cf_put_refer(&cr, 0x81, 2); /* Textual description > unit */ > cf_put_keyval(&cr, 0x0c, 0x0083c0); /* Node capabilities */ > /* NOTE: Add other unit referers here, and append at bottom */ > //cf_put_keyval(&cr, 0x04, 0x991029); > //cf_put_keyval(&cr, 0x0A, 0x00094B); > cf_put_keyval(&cr, 0x0B, 0x000802); > cf_unit_end(&cr); > > /* Textual description - "Linux 1394" */ > cf_unit_begin(&cr, 2); > cf_put_keyval(&cr, 0, 0); > cf_put_1quad(&cr, 0); > cf_put_str(&cr, "FillFactory NV"); > cf_unit_end(&cr); > > ohci->csr_config_rom_length = cr.data - > ohci->csr_config_rom_cpu; } > > Thanks already! > > Pieter > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Alex M. <dem...@th...> - 2003-07-22 08:21:45
|
-- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 |
From: David F. <df...@us...> - 2003-10-20 21:50:37
|
Hello all -- I'm sorry once again to bother you with a newbie question, but I'm wondering if anyone knows whether I can boot from a firewire disk. I have an IBM-PC compatible that is already running Windows, I don't want to repartition that drive, and I don't have room for another internal, so I'm thinking of hooking a LaCie firewire external to it and installing Linux on that, but I can't seem to find any documentation indicating that it is possible to boot from it... does anyone know if it's possible and if so, is there any reference to a how-to or FAQ entry about this? Thanks in advance, David Favro Meta-Dynamic Solutions |
From: Stefan R. <st...@s5...> - 2003-10-21 03:07:02
|
On 20 Oct, David Favro was: > [...] wondering if > anyone knows whether I can boot from a firewire disk. I have an IBM-PC > compatible that is already running Windows, I don't want to repartition that > drive, and I don't have room for another internal, so I'm thinking of hooking a > LaCie firewire external to it and installing Linux on that, [...] The firmware of Apple Macintosh computers can boot from Firewire disks. The BIOSes of IBM compatibles cannot. Or at least I heard of no such BIOS yet. As a workaround, you could shrink one of the existing partitions a bit and install kernel and an initial RAM disk (initrd) in a new partition. Some newer Linux OS distributions come with tools that can resize even NTFS partitions. Or you could put kernel and initrd on a bootable CD. The rest of the Linux installation can then reside on the Firewire disk. The initrd would be needed to set up a minimal system that is able to load sbp2 and perhaps other modular drivers, attach the Firewire disk to the scsi subsystem, mount the partition, and then exchange the initrd root filesystem by the root filesystem on the Firewire disk. Some people did that already, and with some deeper searching you might even find their posts to this list in the archive at sf.net or here: http://marc.theaimsgroup.com/?l=linux1394-user That said, Knoppix might be a better start, provided your PC can boot from a CD-ROM drive. http://www.knopper.net/knoppix/ -- Stefan Richter -=====-=--== =-=- =-=-= http://arcgraph.de/sr/ |
From: Keith H. <hn...@ho...> - 2003-11-13 14:10:08
|
Stefan Richter wrote: > On 20 Oct, David Favro was: > >>[...] wondering if >>anyone knows whether I can boot from a firewire disk. I have an IBM-PC >>compatible that is already running Windows, I don't want to repartition that >>drive, and I don't have room for another internal, so I'm thinking of hooking a >>LaCie firewire external to it and installing Linux on that, [...] > > > The firmware of Apple Macintosh computers can boot from Firewire > disks. The BIOSes of IBM compatibles cannot. Or at least I heard > of no such BIOS yet. > I haven't tried this yet, but it sounds like a promising alternative... http://www.linuxbios.org/ -- Lost in Tokyo, Keith |
From: Daniel P. <da...@ri...> - 2003-10-21 04:06:04
|
On Mon, 20 Oct 2003, David Favro wrote: > I'm sorry once again to bother you with a newbie question, but I'm > wondering if anyone knows whether I can boot from a firewire disk. Not without BIOS support, and I have never seen an x86 BIOS that does feature that support. > I have an IBM-PC compatible that is already running Windows, I don't > want to repartition that drive, and I don't have room for another > internal, so I'm thinking of hooking a LaCie firewire external to it > and installing Linux on that, but I can't seem to find any > documentation indicating that it is possible to boot from it... You can't boot directly from the 1394 device, but you *can* probably work around the problem with a bit of creativity. You probably need a 2.6.0-test* kernel for this, but you /may/ get 2.4 plus initrd working. If you build a boot disk with enough support for 1394 that it can find the device before mounting the root filesystem, you should be able to boot off a floppy (or emulated floppy on CD-ROM) and use the external disk as your root... Daniel -- `geek' --- a carnival performer often billed as a wild man whose act usually includes biting the head off a live chicken or snake. -- Webster's New Collegiate Dictionary, edition 1977 |
From: Chandan_Saikia@URSCorp.com - 2004-01-15 20:02:22
|
Please take me off the list. THanks |
From: Geoffrey <eso...@3t...> - 2004-01-15 20:16:43
|
Chandan_Saikia@URSCorp.com wrote: > Please take me off the list. If you'll follow the link below that is in every posting to the list, you'll find the page that will permit you to do this yourself. > > THanks > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux1394-user > > -- Until later, Geoffrey eso...@3t... Building secure systems inspite of Microsoft |
From: Bilbao J. <JB...@ik...> - 2004-10-05 10:38:55
|
_______________________________________________________________________ Josu Bilbao Ugalde =09 Communications area =09 IKERLAN Technological Research Center =09 P=BA J. M. Arizmendiarrieta, 2 20500 Arrasate-Mondrag=F3n (Gipuzkoa, Spain) Tel.: +34 943 71 24 00 Fax: +34 943 79 69 44 ext: 375 E-mail: jb...@ik... http: www.ikerlan.es _______________________________________________________________________ |