On Wed, Jul 9, 2014 at 2:23 PM, One Thousand Gnomes
wrote:
>> I like the sound of going to the standard ttyS notation and only
>> providing ports for ones that exist, but is this userspace-visible
>
> ttyS is 8250 compatible UARTS.
>
> If the Samsung is not an 8250 compatible UART then it doesn't
On Wed, Jul 9, 2014 at 2:23 PM, One Thousand Gnomes
gno...@lxorguk.ukuu.org.uk wrote:
I like the sound of going to the standard ttyS notation and only
providing ports for ones that exist, but is this userspace-visible
ttyS is 8250 compatible UARTS.
If the Samsung is not an 8250 compatible
> I like the sound of going to the standard ttyS notation and only
> providing ports for ones that exist, but is this userspace-visible
ttyS is 8250 compatible UARTS.
If the Samsung is not an 8250 compatible UART then it doesn't belong as
ttyS from the kernel perspective.
How your udev handles
I like the sound of going to the standard ttyS notation and only
providing ports for ones that exist, but is this userspace-visible
ttyS is 8250 compatible UARTS.
If the Samsung is not an 8250 compatible UART then it doesn't belong as
ttyS from the kernel perspective.
How your udev handles it
On 08.07.2014 10:32, Daniel Drake wrote:
> Hi,
>
> How can we move forward here?
Greg, Jiri, what do you think?
>
> On Thu, Jun 26, 2014 at 1:02 PM, Tomasz Figa wrote:
>> - basically Samsung UART already has its own namespace (ttySAC) and the
>> order inside it is well-defined - instance ID
Hi,
How can we move forward here?
On Thu, Jun 26, 2014 at 1:02 PM, Tomasz Figa wrote:
> - basically Samsung UART already has its own namespace (ttySAC) and the
> order inside it is well-defined - instance ID shall be the hardware
> instance number as specified by documentation. The ports vary
Hi,
How can we move forward here?
On Thu, Jun 26, 2014 at 1:02 PM, Tomasz Figa t.f...@samsung.com wrote:
- basically Samsung UART already has its own namespace (ttySAC) and the
order inside it is well-defined - instance ID shall be the hardware
instance number as specified by documentation.
On 08.07.2014 10:32, Daniel Drake wrote:
Hi,
How can we move forward here?
Greg, Jiri, what do you think?
On Thu, Jun 26, 2014 at 1:02 PM, Tomasz Figa t.f...@samsung.com wrote:
- basically Samsung UART already has its own namespace (ttySAC) and the
order inside it is well-defined -
On 26.06.2014 13:39, Russell King - ARM Linux wrote:
> On Thu, Jun 26, 2014 at 01:24:32PM +0200, Tomasz Figa wrote:
>> Current Samsung UART driver relies on probe order of particular
>> samsung-uart instances, which makes it impossible to get proper
>> initialization of ports when not all ports
On Thu, Jun 26, 2014 at 01:24:32PM +0200, Tomasz Figa wrote:
> Current Samsung UART driver relies on probe order of particular
> samsung-uart instances, which makes it impossible to get proper
> initialization of ports when not all ports are available on board,
> not even saying of deterministic
Current Samsung UART driver relies on probe order of particular
samsung-uart instances, which makes it impossible to get proper
initialization of ports when not all ports are available on board,
not even saying of deterministic device naming.
This series intends to fix this situation by adding
Current Samsung UART driver relies on probe order of particular
samsung-uart instances, which makes it impossible to get proper
initialization of ports when not all ports are available on board,
not even saying of deterministic device naming.
This series intends to fix this situation by adding
On Thu, Jun 26, 2014 at 01:24:32PM +0200, Tomasz Figa wrote:
Current Samsung UART driver relies on probe order of particular
samsung-uart instances, which makes it impossible to get proper
initialization of ports when not all ports are available on board,
not even saying of deterministic
On 26.06.2014 13:39, Russell King - ARM Linux wrote:
On Thu, Jun 26, 2014 at 01:24:32PM +0200, Tomasz Figa wrote:
Current Samsung UART driver relies on probe order of particular
samsung-uart instances, which makes it impossible to get proper
initialization of ports when not all ports are
14 matches
Mail list logo