archive-org.com » ORG » N » NETBSD.ORG

Total: 1243

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Playing With Sensors
    Multi position keylocks receiving the german DCF77 time signal station maybe using GPIO pins to build a 1 Wire bus 1 Wire bus Digital thermometers Hardware Notes Soekris net4801 GPIO pins wrong in manual The GPIO Pins in the Soekris net4801 manual are utterly wrong at least there is a manual unlike for the net5501 although one with many errors JP5 Pin PC87366 Pin JP5 Pin PC87366 Pin JP5 Pin PC87366 Pin JP5 Pin C87366 Pin 3 GPIO16 4 GPIO17 5 GPIO18 6 GPIO19 7 GPIO20 8 GPIO21 9 GPIO22 10 GPIO23 Connecting a LCD module to the 4801 JP5 This example assumes a DIP162 module LCD 4801 Function PC87366 Pin 1 11 GND 2 2 VCC 3 nc VEE Kontrast 4 12 RS GPIO8 GPIO4 5 13 RW GPIO9 GPIO5 6 15 Enable GPIO10 GPIO13 7 3 D0 Display Data LSB GPIO0 GPIO16 8 4 D1 GPIO1 GPIO17 9 5 D2 GPIO2 GPIO18 10 6 D3 GPIO3 GPIO19 11 7 D4 GPIO4 GPIO20 12 8 D5 GPIO5 GPIO21 13 9 D6 GPIO6 GPIO22 14 10 D7 GPIO7 GPIO23 15 nc 16 nc 17 nc LED 18 nc LED Connecting a DS18B20 to Soekris 5501 JP5 DS18B20 Vin 1 2

    Original URL path: http://wiki.netbsd.org/users/mbalmer/sensors/ (2016-02-01)
    Open archived version from archive

  • mef
    The Guide Manual pages Wiki Support Problem report guide Report a bug Query bug database Security Community Blogs Mailing lists List archives Developers Browse source Cross reference Release engineering Projects list Ports History Emulators Packages Browse packages Release engineering Wiki Home Edit Comment Source History New RecentChanges NetBSD Wiki users mef Makoto Fujiwara pkgsrc project check update PR not submitted PR submitted or concerned Add a comment Last edited Monday

    Original URL path: http://wiki.netbsd.org/users/mef/ (2016-02-01)
    Open archived version from archive

  • minskim
    Advocacy Documentation FAQ HOWTOs The Guide Manual pages Wiki Support Problem report guide Report a bug Query bug database Security Community Blogs Mailing lists List archives Developers Browse source Cross reference Release engineering Projects list Ports History Emulators Packages Browse packages Release engineering Wiki Home Edit Comment Source History New RecentChanges NetBSD Wiki users minskim TeX Live for pkgsrc Add a comment Last edited late Thursday evening July 28th 2011

    Original URL path: http://wiki.netbsd.org/users/minskim/ (2016-02-01)
    Open archived version from archive

  • Michael van Elst (mlelstv@NetBSD.org)
    a bug Query bug database Security Community Blogs Mailing lists List archives Developers Browse source Cross reference Release engineering Projects list Ports History Emulators Packages Browse packages Release engineering Wiki Home Edit Comment Source History New RecentChanges NetBSD Wiki users Michael van Elst mlelstv NetBSD org 1 Device naming the first Device naming the second Disk interfaces in the kernel Using large disks Disk driver template 2 Supported video 3

    Original URL path: http://wiki.netbsd.org/users/mlelstv/ (2016-02-01)
    Open archived version from archive

  • device-naming
    Concurrent autoconfiguration might even generate unpredictable unit numbers without any intervention Partitions on device names are just private counts a b c per device Partition suffixes are just indexes into a table that describes slices of a disk There is always a specific slice RAW PART that covers that whole disk It is usually not used for filesystems but for meta information like the disk label itself On some disks the partition table is computed from disk parameters instead of read from persistent storage But this is supposed to be a stable mapping Partition suffixes however are not portable because they are based on labels that depend on the machine or even individual drivers Wedges are partitions that look like units of a single driver A wedge is a pseudo disk that accesses the RAW PART of a real disk This effectively bypasses the driver based partitioning and is used to provide a driver independent partitioning system in particular to support foreign disk labels Since wedges are subject to the same autoconf naming scheme we now have a disk driver name that is always dk and has no connection to the accessed hardware There is a this time global unit number for all disks and of course no partition suffix You must predict the order of wedge attachments to be able to access a particular disk Wedge names Wedges are a unified interface to partitions In a wedge enabled system each disk partition is referenced by a wedge This is a very simple view on a range of disk blocks In particular there is no meta information except for the simple geometry describing the size of a block and the total number of blocks Wedges reflect all the data and meta data that is required to provide storage used by a filesystem Wedges can have a name which defaults to a UUID Wedges are units of the dk driver and can be identified by a name The name is a string that uniquely identifies the unit and must be given to the unit when it is attached The attachment will fail when the name already exists When a wedge is created manually the name is given by the operator to the dkctl command When a wedge is created by the autodetect code the names are taken or computed from the detected label In particular MBR partitions generate the wedge name from driver unit partition suffix of the underlying disk where the suffixes start with e to avoid conflicts This looks like a conventional partition name e g sd3f BSD disklabel partitions do something similar but also check for the volume name in the disklabel If there is a volume name and it is not the default string fictitious then the wedge name is built from volume and partition suffix separated by a e g system f for partition 6 of the volume named system Otherwise it is built from driver unit and partition suffix This again looks like a conventional

    Original URL path: http://wiki.netbsd.org/users/mlelstv/device-naming/ (2016-02-01)
    Open archived version from archive

  • device-naming2
    Edit Comment Source History New RecentChanges NetBSD Wiki users mlelstv device naming2 udevpubd Hook into kernel to learn about autoconfigured devices Adds missing device entries in dev by calling MAKEDEV Maintains symlinks to device entries in dev wedges Automounter Provides a namespace mount unmount for unprivileged users by internal function or by external program that extends functionality program is a safeguard filesystem autodetection fsck amd is old but smart conditional

    Original URL path: http://wiki.netbsd.org/users/mlelstv/device-naming2/ (2016-02-01)
    Open archived version from archive

  • disk-devices-layered
    stop d tty d poll d kqfilter constants d flag Layering is possible the dk lookup function is used to get a handle a vnode a child device call each other using vnode layer methods VOP IOCTL VOP STRATEGY dk lookup to find vnode vn close to release vnode Disk drivers use the kernel disk interface to provide information for iostat and property lists There are also helper routines to handle partitions and to get a disklabel kernel disk interface kern subr disk c driver calls disk init to register instrumentation iostat DIOCGDISKINFO partition support bounds check disklabel routines low level routines polluting namespace disk read sectors registers a callback to strategy and minphys functions currently there are only one user dk 4 calls the minphys function Almost all disk drivers have a regular driver structure that is created by the autoconf framework An exception is the ccd 4 driver that hand crafts its private data without autoconf autoconf device building kern subr autoconf c generic for all device drivers not only disk drivers provides common data including a proplib dictionary the dictionary is used to register unit data for example a drive geometry The disklabel routines are mostly MD the sun sparc routines are not in arch but in dev sun the i386 amd64 routines also used by other archs are in kern subr disk mbr c disklabel routines really MD implement readdisklabel writedisklabel setdisklabel kern subr disk mbr c more disklabel routines MBR ISO9660 writedisklabel sun disksubr c like subr disk mbr c but different for sun3 sparc sparc64 arch disksubr c like subr disk mbr c but different A wedge is a layered device on top of the RAW PART of a standard disk device All disk drivers need to implement ioctls to manually attach wedge devices

    Original URL path: http://wiki.netbsd.org/users/mlelstv/disk-devices-layered/ (2016-02-01)
    Open archived version from archive

  • disk-driver-template
    error config cfattach attach xxx cd cd name xxx ca if error aprint error s unable to register cfattach d n xxx cd cd name error return some global initialization endif static device t xxx create int unit cfdata t cf device t dv cf malloc sizeof cf M DEVBUF M WAITOK cf cf name xxx cd cd name cf cf atname xxx cd cd name cf cf unit unit cf cf fstate FSTATE STAR dv config attach pseudo cf if dv NULL aprint error s failed to attach pseudo device n xxx cd cd name free cf M DEVBUF return dv static int xxx destroy device t dv int error cfdata t cf cf device cfdata dv error config detach dev DETACH QUIET if error return error free cf M DEVBUF return 0 endif static int xxxopen dev t dev int flags int fmt struct lwp l DEVPROLOG return dk open dksc dev flags fmt l static int xxxclose dev t dev int flags int fmt struct lwp l DEVPROLOG return dk close dksc dev flags fmt l static int xxxread dev t dev struct uio uio int ioflag return physio xxxstrategy NULL dev B READ xxxminphys uio static int xxxwrite dev t dev struct uio uio int ioflag return physio xxxstrategy NULL dev B WRITE xxxminphys uio static int xxxioctl dev t dev u long cmd void addr int32 t flag struct lwp l int error DEVPROLOG error dk ioctl dksc dev cmd addr flag l if error EPASSTHROUGH return error error 0 switch cmd private IOCTLs default error ENOTTY return error static void xxxstrategy struct buf bp DEVPROLOG dk strategy dksc bp static int xxxdiscard dev t dev off t pos off t len DEVPROLOG return dk discard dksc dev pos len static int xxxsize dev t dev DEVPROLOG return dk size dksc dev static int xxxdump dev t dev daddr t blkno void va size t size DEVPROLOG return dk dump dksc dev blkno va size static void xxxminphys struct buf bp struct xxx softc sc int unit unit DISKUNIT bp b dev if sc device lookup private xxx cd unit NULL return xxx iosize sc sc dv bp b count minphys bp I O callback static void xxxdone struct xxx softc sc struct buf bp struct dk softc dksc sc sc dksc dk done dksc bp dk start dksc NULL Startup and Shutdown static int xxx init device t self struct xxx softc sc device private self struct dk softc dksc sc sc dk dk init dksc self DKTYPE xxx disk init dksc sc dkdev dksc sc xname xxdkdriver dk attach dksc disk attach dksc sc dkdev initialize dksc sc dkdev dk geom bufq alloc dksc sc bufq BUFQ DISK DEFAULT STRAT BUFQ SORT RAWBLOCK possibly deferred with config interrupts dkwedge discover dksc sc dkdev return 0 static int xxx finish device t self struct xxx softc sc device private self struct dk softc dksc sc sc dksc dkwedge delall dksc sc dkdev dk drain

    Original URL path: http://wiki.netbsd.org/users/mlelstv/disk-driver-template/ (2016-02-01)
    Open archived version from archive