| /freebsd/sys/cam/ctl/ |
| H A D | ctl_tpc_local.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_frontend_ioctl.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_backend.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_backend.h | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_frontend.h | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_frontend.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_frontend_cam_sim.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_backend_ramdisk.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | scsi_ctl.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_private.h | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_backend_block.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl_frontend_iscsi.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|
| H A D | ctl.c | 0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
0c629e28 Sat Jan 21 19:38:26 GMT 2017 Alexander Motin <mav@FreeBSD.org> Add initial support for CTL module unloading.
It is only a first step and not perfect, but better then nothing.
The main blocker is CAM target frontend, that can not be unloaded,
since CAM does not have mechanism to unregister periph driver now.
MFC after: 2 weeks
|