> OK, understood.  How about having MD sub-routine in the same interface
> (say acpi_set_resources() or acpi_create_instance() or whatever) for
> i386 and ia64?  Then generic ACPI identify method calls suitable
> sub-routine depending on machine architecture.
>  - i386/i386/acpi_machdep.c
>       acpi_set_resources() (ex-acpiprobe_identify())
>  - ia64/ia64/acpi_machdep.c
>       acpi_set_resources()
>  - dev/acpi/acpi.c
>       acpi_identify()
>               this is quite simple, just do simple error checking and
>               call acpi_set_resources() then return.
> Is this good for you too?

It's closer.  I just realised that we need a way of creating resources 
for SystemIO and SystemMemory AML objects as well.  I think I've worked 
this out too; I'll try to get it worked out today and send you a patch 
this evening.  I'm following your request to get the bus-dependant parts 
split out, but I do *not* think that we should be committing any of the 
NetBSD code to the FreeBSD source tree (this has been a failure in the 
past), or vice versa.

Meanwhile, my laptop is getting very hot. 8)

... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to