[Top] [All Lists]

Re: [PATCH] RM9000 serial driver

To: "Russell King" <>
Subject: Re: [PATCH] RM9000 serial driver
From: Thomas Koeller <>
Date: Wed, 30 Aug 2006 23:28:47 +0200
Cc: "Sergei Shtylyov" <>, "Yoichi Yuasa" <>,,,, Thomas Köller <>
In-reply-to: <>
Organization: Basler AG
Original-recipient: rfc822;
References: <> <> <>
User-agent: KMail/1.9.3
On Wednesday 30 August 2006 14:12, Russell King wrote:

> iotype is all about the access method used to access the registers of
> the device, be it by byte or word, and it also takes account of any
> variance in the addressing of the registers.
> It does not refer to features or bugs in any particular implementation.

That's what I assumed, too - it seemed obvious. And it seemed equally
obvious that it is the port type that encodes the the implementation's
peculiarities. Among these are the register offset mapping requirements,
so I assumed these should depend on the port type as well.

Now Sergei strongly insist that it's the iotype that should be checked
whenever to get to the hardware type. I still do not quite understand how
that is supposed to work. If I have a PCI device, for example, then the
iotype will always be either UPIO_MEM or UPIO_PORT, so how could I learn
something about the hardware implementation by looking at these values?
Or is the assumption that devices on a standard bus will always be of
a standard type?


Thomas Koeller, Software Development

Basler Vision Technologies
An der Strusbek 60-62
22926 Ahrensburg

Tel +49 (4102) 463-390
Fax +49 (4102) 463-46390

<Prev in Thread] Current Thread [Next in Thread>