In SO that write 2 years ago in high-shool,
I have to investigate if is To be convenient unife the keyboard and video modules,
for me Not, but what how to response about this?
the files are: video.c and keyboard.c
all have to function that return data type void and int
thanks, Alejandro
is possible To unify keyboards and video modules in SO
is possible To unify keyboards and video modules in SO
- Attachments
-
- keyboard and viedo in C.zip
- (10 KiB) Downloaded 24 times
-
Kevin McGuire
- Member
- Posts: 843
- Joined: Tue Nov 09, 2004 12:00 am
- Location: United States
- Contact:
I need to know, "Why unify keyword and monitor?" to understand what you might be talking about.
Unification Through Abstraction
I imagine you could unify the keyword, video, mouse, and other devices under a subsystem such as Human Interface Devices. Such that the HID subsystem becomes responsible for exposing, configuring, making default device selections, and marshaling interaction to these devices (or module instances for particular devices).
Unification Of Device Control Code Or Functionality
In this case I am not sure, but I would think it would be very difficult to combine two driver into one that controls two difference pieces of hardware. I mean what if you had Monitor Vendor A and Keyboard Vendor Z in one driver, and someone uses your driver and has a Monitor Vendor B with a different chipset. This would defeat the purpose of actually separating things into loadable drivers.
The only area where I could see this happening is if a single computer attachment or board provided two different devices and as such you wrote a driver for this attachment or board that could control these physically attached devices?
Unification Of Driver Interface For Functionality
I am not sure how you could unify the functionality of a monitor and keyword since they appear to me as two completely different devices. They have completely different functionality which equates down to a different set of functions, methods, commands, or such other that they support.
PS:
You might have to write in your native language, and hope someone here can understand it and translate it since you appear to be having trouble explaining your question.
Unification Through Abstraction
I imagine you could unify the keyword, video, mouse, and other devices under a subsystem such as Human Interface Devices. Such that the HID subsystem becomes responsible for exposing, configuring, making default device selections, and marshaling interaction to these devices (or module instances for particular devices).
Unification Of Device Control Code Or Functionality
In this case I am not sure, but I would think it would be very difficult to combine two driver into one that controls two difference pieces of hardware. I mean what if you had Monitor Vendor A and Keyboard Vendor Z in one driver, and someone uses your driver and has a Monitor Vendor B with a different chipset. This would defeat the purpose of actually separating things into loadable drivers.
The only area where I could see this happening is if a single computer attachment or board provided two different devices and as such you wrote a driver for this attachment or board that could control these physically attached devices?
Unification Of Driver Interface For Functionality
I am not sure how you could unify the functionality of a monitor and keyword since they appear to me as two completely different devices. They have completely different functionality which equates down to a different set of functions, methods, commands, or such other that they support.
PS:
You might have to write in your native language, and hope someone here can understand it and translate it since you appear to be having trouble explaining your question.
Muchas Gracias Kevin!!!
Te comento, en un Sistema Operativo que se esta desarrollando en la universidad, de proposito general, estoy investigando, si es conveniente unificar los modulos teclado y video, actualmente estan trabajando por separado, en los archivos que adjunte se puede ver el codigo.
La idea es debatir con alguien que entiende el tema un poco mas en profundidad,
para mi es mejor que trabajen por separados, estoy tratando de encontrar justificaciones acerca de esta afirmacion.
muchas gracias
Alejandro
Te comento, en un Sistema Operativo que se esta desarrollando en la universidad, de proposito general, estoy investigando, si es conveniente unificar los modulos teclado y video, actualmente estan trabajando por separado, en los archivos que adjunte se puede ver el codigo.
La idea es debatir con alguien que entiende el tema un poco mas en profundidad,
para mi es mejor que trabajen por separados, estoy tratando de encontrar justificaciones acerca de esta afirmacion.
muchas gracias
Alejandro
Puedes explicar mejor lo que entiendes por unificar?ancaya wrote:Muchas Gracias Kevin!!!
Te comento, en un Sistema Operativo que se esta desarrollando en la universidad, de proposito general, estoy investigando, si es conveniente unificar los modulos teclado y video, actualmente estan trabajando por separado, en los archivos que adjunte se puede ver el codigo.
La idea es debatir con alguien que entiende el tema un poco mas en profundidad,
para mi es mejor que trabajen por separados, estoy tratando de encontrar justificaciones acerca de esta afirmacion.
muchas gracias
Alejandro
en principio son dos cosas muy distintas.
-
Kevin McGuire
- Member
- Posts: 843
- Joined: Tue Nov 09, 2004 12:00 am
- Location: United States
- Contact: