-- Forwarded message --
From: william wallace <[EMAIL PROTECTED]>
Date: Jun 7, 2006 11:13 AM
Subject: Re: misc questions about the device&driver arch
To: "M. Warner Losh" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], Scott Long <[EMAIL PROTECTED]>
#x27;s a find document for the freebsd resource topology,
thank you ,sir .
On 6/4/06, M. Warner Losh <[EMAIL PROTECTED]> wrote:
In message: <[EMAIL PROTECTED]>
"william wallace" <[EMAIL PROTECTED]> writes:
: On 5/20/06, Warner L
On 6/4/06, M. Warner Losh <[EMAIL PROTECTED]> wrote:
In message: <[EMAIL PROTECTED]>
: > > > Warner
: Prior to removing a card from the system, two things must occur:
:
: The device's driver must cease accessing the card.
:
: The card must cease generation transaction and interrupts.
:
: How this
On 5/20/06, Warner Losh <[EMAIL PROTECTED]> wrote:
From: "william wallace" <[EMAIL PROTECTED]>
Subject: Re: misc questions about the device&driver arch
Date: Sat, 20 May 2006 13:39:08 +0800
> comparing the method array of pci_pci and cardbusbridge:
> what
Sir :
question one :
I see lots' of use of pcib_get_bus but i cannot see the
defination ,where is it ?
question two:
what is the relationship among 1device_delete_child
2devclass_delete_device and 3devclass_delete_driver
there seems some overlap among them :)
1devclass_delete_driver ->de
eeBSD ,
that is what i am doing,thank u
On 5/31/06, M. Warner Losh <[EMAIL PROTECTED]> wrote:
In message: <[EMAIL PROTECTED]>
"william wallace" <[EMAIL PROTECTED]> writes:
: BTW :my current code is mainly translate the pcie natve hotplug from
: linux , not f
thank sir ,below is my opinion
On 5/30/06, Scott Long <[EMAIL PROTECTED]> wrote:
On Tue, 30 May 2006, william wallace wrote:
> On 5/30/06, Scott Long <[EMAIL PROTECTED]> wrote:
>> william wallace wrote:
>
>> >>
>> > I have to clarify my intentions t
On 5/30/06, Scott Long <[EMAIL PROTECTED]> wrote:
M. Warner Losh wrote:
> : THIRD
> : Because the PCIE configure space is 4k long ,shall we change the
> : #define PCI_REGMAX 255
> : to facilitate the PCI express config R/W?
>
> Maybe. Lemme investigate because PCIe changes this from a well know
On 5/30/06, M. Warner Losh <[EMAIL PROTECTED]> wrote:
In message: <[EMAIL PROTECTED]>
"william wallace" <[EMAIL PROTECTED]> writes:
: Sir：
: I have got the way to map linux pci access way to the BSD way :)
: now ,several more question ,wondering :(
Sir：
I have got the way to map linux pci access way to the BSD way :)
now ,several more question ,wondering :(
FIRST
struct pci_devinfo * pci_read_device(device_t pcib, int b, int s, int
f, size_t size)
struct cardbus_devinfo {
struct pci_devinfo pci;
uint8_tmprefetchable;
t dev, int b, int s, int f, int
reg, int width) ?
and how can i get int b, int s, int f?
thank u
On 5/24/06, John-Mark Gurney <[EMAIL PROTECTED]> wrote:
william wallace wrote this message on Wed, May 24, 2006 at 21:13 +0800:
> roger really good tips :)
> and so far as i know ,
> the
;
typedef u_int32_t u32;
so ,what is the use of drm_os_freebsd.h
and any advice for me to translate DT from linux to Freebsd?
On 5/24/06, John-Mark Gurney <[EMAIL PROTECTED]> wrote:
william wallace wrote this message on Wed, May 24, 2006 at 21:13 +0800:
> roger really good tips :)
> and
wrote:
william wallace wrote this message on Wed, May 24, 2006 at 15:48 +0800:
> IN static device_method_t pci_methods[] = {
> what is the freeBSD's magic to connect pci_read_config_methodwtih
> PCI_READ_CONFIG? awk script?and so on?
> which
> DEVMETHOD(pci_read_config,p
); in
pci_enable_io_method in pci.c
and what if i create a new method in pci method interface ?
such as DEVMETHOD(pci_have_rest , pci_have_rest_method)
what else should i do when i want to use PCI_HAVE_REST(dev ) point to
pci_have_rest_method
On 5/23/06, Scott Long <[EMAIL PROTECTED]> wrote:
will
I just have fossicked some idea from [EMAIL PROTECTED] "PCI-Express support "
PCI-Express support
All,
I've emailed before about supporting various aspects of PCI-Express and
especially MSI, but haven't really gotten too far with it due to lack of
resources. I now how access to a system that c
On 5/22/06, Warner Losh <[EMAIL PROTECTED]> wrote:
From: "william wallace" <[EMAIL PROTECTED]>
Subject: Re: misc questions about the device&driver arch
Date: Sun, 21 May 2006 16:08:00 +0800
> On 5/21/06, Warner Losh <[EMAIL PROTECTED]> wrote:
> > nope
On 5/21/06, Warner Losh <[EMAIL PROTECTED]> wrote:
nope. It may be called once per bus instance per driver, if the bus
is not self-identifying. If the bus is self-idntiying, chances are
that it will not be called. pci never calls its children drivers'
identify routine because it already knows
bus): DEVMETHOD(bus_add_child,ppbus_add_child),
Smbus.c (dev\smbus):DEVMETHOD(bus_add_child,smbus_add_child),
On 5/20/06, Warner Losh <[EMAIL PROTECTED]> wrote:
From: "william wallace" <[EMAIL PROTECTED]>
Subject: Re: misc questions about the device&driver arc
On 5/20/06, Warner Losh <[EMAIL PROTECTED]> wrote:
Busses create devices to represent hardware in the system. The bus
then causes these devices to be probed and attached. This latter
usage is for those cases. As drivers are loaded these devices are
offered to the new (and old) drivers in the
comparing the method array of pci_pci and cardbusbridge:
what losts in pci bridge but exist in cardbusbridge:
1 card interface
2 power interface
3 some functions :
3ain bus interface
(bus_driver_added, cbb_driver_added),
(bus_child_detached,cbb_child_detac
about devclass_find_internal
devclass_find_internal will be called to create a new devclass in
such 2 conditions :
one is creating a new device , as : if (name) { dc =
devclass_find_internal(name, 0, TRUE);
another is in the function:devclass_add_driver. but ,if a driver 's
name is different f
21 matches
Mail list logo
