tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: bus_space_physload(9)

To: Masao Uebayashi <uebayasi%tombi.co.jp@localhost>
Subject: Re: bus_space_physload(9)
From: Jason Thorpe <thorpej%shagadelic.org@localhost>
Date: Thu, 15 Apr 2010 18:11:06 -0700

On Mar 24, 2010, at 8:04 AM, Masao Uebayashi wrote:

> It's in bus_space(9) because it's API for device drivers.  Its behavior needs
> UVM's help, of course.

Also, because bus-specific code needs to map the bus_space_tag_t + the 
bus_addr_t into a system physical address.

-- thorpej

References:
- Re: bus_space_physload(9)
  - From: Masao Uebayashi
- re: bus_space_physload(9)
  - From: matthew green
- Re: bus_space_physload(9)
  - From: Masao Uebayashi

Prev by Date: Re: panic: ffs_valloc: dup alloc
Next by Date: Re: multiprocessor routing problem
Previous by Thread: Re: bus_space_physload(9)
Next by Thread: Re: bus_space_physload(9)
Indexes:

Home | Main Index | Thread Index | Old Index