개요

• 솔라나라에 설명된 어플리케이션에 대해 맨 페이지를 찾아 출력한다.
• MAN 페이지에 대한 설명은 윈디하나의 솔라나라: MAN 페이지을 참고하자.
• svcadm(1M)을 검색하려면 섹션에서 1M 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.

ddi_poke(9f)

ddi_poke(9F)                   Kernel Functions                   ddi_poke(9F)



NAME
       ddi_poke,  ddi_poke8,  ddi_poke16,  ddi_poke32,  ddi_poke64, ddi_pokec,
       ddi_pokes, ddi_pokel, ddi_poked - write a value to a location

SYNOPSIS
       #include <sys/ddi.h>
       #include <sys/sunddi.h>

       int ddi_poke8(dev_info_t *dip, int8_t *addr, int8_t value);


       int ddi_poke16(dev_info_t *dip, int16_t *addr, int16_t value);


       int ddi_poke32(dev_info_t *dip, int32_t *addr, int32_t value);


       int ddi_poke64(dev_info_t *dip, int64_t *addr, int64_t value);

INTERFACE LEVEL
       Solaris DDI  specific  (Solaris  DDI).  The  ddi_pokec(),  ddi_pokes(),
       ddi_pokel(), and ddi_poked() functions are obsolete. Use, respectively,
       ddi_poke8(), ddi_poke16(), ddi_poke32(), and ddi_poke64(), instead.

PARAMETERS
       dip      A pointer to the device's dev_info structure.


       addr     Virtual address of the location to be written to.


       value    Value to be written to the location.


DESCRIPTION
       These routines cautiously attempt to write a value to a specified  vir‐
       tual  address,  using  the parent nexus driver to assist in the process
       where necessary.


       If the address is not valid, or the value cannot be written without  an
       error occurring, an error code is returned.


       These routines are most useful when first trying to establish the pres‐
       ence of a given device  on  the  system  in  a  driver's  probe(9E)  or
       attach(9E) routines.


       On  multiprocessing  machines  these  routines  can be extremely heavy-
       weight, so use the ddi_peek(9F) routines instead if possible.

RETURN VALUES
       DDI_SUCCESS    The value was successfully written to the given  virtual
                      address.


       DDI_FAILURE    An error occurred while trying to write to the location.


CONTEXT
       These functions can be called from user, interrupt, or kernel context.

SEE ALSO
       attach(9E), probe(9E), ddi_peek(9F)


       Writing Device Drivers in Oracle Solaris 11.4

NOTES
       The  functions  described  in this manual page previously used symbolic
       names which specified their data access size; the function  names  have
       been  changed so they now specify a fixed-width data size. See the fol‐
       lowing table for the new name equivalents:


       tab() box; lw(2.75i) lw(2.75i) Previous NameNew Name ddi_pokecddi_poke8
       ddi_pokesddi_poke16 ddi_pokelddi_poke32 ddi_pokedddi_poke64




Oracle Solaris 11.4               16 Jan 2006                     ddi_poke(9F)