> Date: Tue, 5 Apr 2016 18:11:03 +0200
> From: Patrick Wildt
>
> Updated to include feedback.
>
> ok?
Looks good to me; ok kettenis@
> diff --git sys/dev/ofw/fdt.c sys/dev/ofw/fdt.c
> index 4cebbb4..09ddcfc 100644
> --- sys/dev/ofw/fdt.c
> +++ sys/dev/ofw/fdt.c
> @@ -34,6
On Sun, Apr 03, 2016 at 06:56:52PM +0200, Mark Kettenis wrote:
> > Date: Sun, 3 Apr 2016 16:57:10 +0200
> > From: Patrick Wildt
> >
> > Hi,
> >
> > now we're able to get a node's memory address. Though, a device tree
> > may implement so called ranges. Those ranges are used
On Sun, Apr 03, 2016 at 06:56:52PM +0200, Mark Kettenis wrote:
> > Date: Sun, 3 Apr 2016 16:57:10 +0200
> > From: Patrick Wildt
> >
> > Hi,
> >
> > now we're able to get a node's memory address. Though, a device tree
> > may implement so called ranges. Those ranges are used
> Date: Sun, 3 Apr 2016 16:57:10 +0200
> From: Patrick Wildt
>
> Hi,
>
> now we're able to get a node's memory address. Though, a device tree
> may implement so called ranges. Those ranges are used to translate from
> one address space to another.
>
> This is used on a few