OpenBSD Journal

Developer Blog: dlg: sili(4) finds a disk for the first time

Contributed by dlg on from the i-thought-wd-was-for-sata-disks dept.

The subject says it all, I just got sili(4) to attach a disk properly:

sili0 at pci3 dev 8 function 0 "CMD Technology SiI3124 SATA" rev 0x01: irq 11
scsibus3 at sili0: 4 targets
sd1 at scsibus3 targ 3 lun 0: <ATA, ST3320620AS, 3.AA> SCSI2 0/direct fixed
sd1: 305245MB, 305245 cyl, 64 head, 32 sec, 512 bytes/sec, 625142448 sec total

I'll spare you the technical details till the driver is closer to being finished, and I'm further away from sleep :)

(Comments are closed)


Comments
  1. By niallo (82.195.149.9) niallo@openbsd.org on

    Great work!

  2. By Anonymous Pilot (161.97.198.84) on

    WELL DONE!

  3. By Anonymous Coward (70.109.50.2) on

    Thanks for the good work.

  4. By gwyllion (193.190.253.129) on

    Wow, a functional driver in 2 weeks. Impressive!

    Comments
    1. By David Gwynne (dlg) on

      > Wow, a functional driver in 2 weeks. Impressive!

      that's not really true, all i did was get small io moving.

      it needs to deal with larger buffers, multiple ios, interrupt driven io, error handling, and lots of other things in between. then it will be functional.

      Comments
      1. By Pierre Riteau (82.248.212.58) on

        I have a "pciide0 at pci1 dev 11 function 0 "CMD Technology SiI3112 SATA" rev 0x02: DMA" on my nForce2 motherboard.
        From linux-ata.org : No TCQ/NCQ. Looks like a PATA controller, but with full SATA control including hotplug and PM.

        Documentation seems available like the other chips (on gkernel.sf.net), have you thought about supporting them if they are similar? If they are quite different I understand you want to focus only on the recent chips.

  5. By Anonymous Coward (202.45.110.141) on

    Where did the source code for this driver *really* come from?

    Where was it stolen from?

    Comments
    1. By Anonymous Coward (67.64.89.177) on

      YOUR MOM

    2. By Anonymous Coward (216.220.225.229) on

      > Where did the source code for this driver *really* come from?
      >
      > Where was it stolen from?
      >

      Don't feed the troll.

    3. By David Gwynne (dlg) on

      > Where did the source code for this driver *really* come from?
      >
      > Where was it stolen from?

      i stole the autoconf stuff from mpi(4), the atascsi interface usage from ahci(4), the ccb concepts from ami(4), and the bus_dma handling from ahci(4), which came via arc(4) from mpi(4) which in turn came from ami(4).

    4. By Anonymous Coward (150.101.159.6) on

      > Where did the source code for this driver *really* come from?
      >
      > Where was it stolen from?
      >

      Same place PF came from Darren.

    5. By Anonymous Coward (65.57.245.11) on

      > Where did the source code for this driver *really* come from?
      >
      > Where was it stolen from?

      Darren - after all these years it is great to know that you still care. Thanks!

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]