[coLinux-devel] [ colinux-Feature Requests-1460439 ] PCI device mapping

[SourceForge.net <no...@so...>]

Feature Requests item #1460439, was opened at 2006-03-28 21:24
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1460439&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: PCI device mapping

Initial Comment:
Implement a Windows PCI device driver that can be
installed on any PCI device in Windows - and a PCI bus
driver in linux. When the device driver is installed on
a device in Windows that device appears on the PCI bus
in linux. This would allow arbitrary PCI devices to be
selected for use in Linux. Now
graphics/sound/USB/wireless can work natively in Linux.

Simon

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-02-27 01:19

Message:
Logged In: NO 

Requirement of this is not cleared for us,please explain this in detail.In
this it is mentioned that we need to implement PCI bus in linux,and PCI
driver in windows.but in the kernal we have some PCI bus driver under
arch/i386/pci know?Please us give us some idea about this

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-02-27 00:42

Message:
Logged In: YES 
user_id=579204
Originator: NO

Reserve a resource on windows side is not the problem. A driver with an
inf file and some ntkernel functions would do this.
But, coLinux has no IO, no DMA and other recourses, and no "forwarder" for
such things.

coLinux has no trap handler for illegal IO to go into windows. All trap
handlers are handled inside Linux self (IO fault, page fault, illegal
instruction). That's why you can not access for example the hardware clock
"hwclock", and why not can see the host BIOS.

The only forwarder are "interrupt-proxy" and allocate "pseudo-physicaly"
memory.


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-02-27 00:15

Message:
Logged In: NO 

I don't know enough about Windows driver design (specifically resource
requests) to know whether this is even possible, because such a driver
would have to request all the IRQs/IO ports/DMA channels and so forth
needed by the hardware, and it might be too late once colinux loads and the
linux driver supplies the device-specific details.

If it is possible to set the resources after colinux loaded, then it
shouldn't break the design, because all hardware access would still go
through the Windows kernel-mode APIs and therefore be properly
synchronized.  It would however be extremely slow unless the device is
designed to be non-chatty (see discussions of emulated I/O ports vs
paravirtualization on the mailing lists of kvm, xen, etc).

----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-02-26 23:56

Message:
Logged In: YES 
user_id=579204
Originator: NO

This is still open.
coLinux has no direct hardware access. *All* io are handled by host
system, includes physically PCI bus and interrupt controller.

Remember, such implementation would break the design.


----------------------------------------------------------------------

Comment By: deepthi kiran (deepthi_kiran)
Date: 2008-02-26 19:38

Message:
Logged In: YES 
user_id=2000870
Originator: NO

Hi,

Is this request still open?we would like to takeup this request if it is
open.PLease respond it soon

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1460439&group_id=98788