From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Andrey Panin <pazke@centrinvest.ru>,
lkml <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: How to access serial port that is set in BIOS as OS Controlled
Date: Sat, 13 Aug 2011 05:59:04 +0800 (SGT) [thread overview]
Message-ID: <Pine.LNX.4.64.1108130553490.22593@boston.corp.fedex.com> (raw)
On Sat, Aug 13, 2011 at 2:07 AM, Bjorn Helgaas <bhelgaas@google.com>
wrote:
> On Fri, Aug 12, 2011 at 1:01 AM, Jeff Chua <jeff.chua.linux@gmail.com>
wrote:
> I think this is all working as expected now. PNP automatically
> configures the port and enables it. The 8250_pnp driver automatically
> claims it. And I assume the port "just works" without any setserial or
> sysfs manipulations at all. Does that solve your issue?
Yes, it solved my issue:) Big thanks to you!
> We need to think a bit more about whether this the right approach for
> handling _SRS and whether it's in the right place. But I think this is
> a start, at least.
Agreed.
Please push the patch to Linus so he can include it to his tree to solve
os-controlled devices so they can automatically be used under Linux.
Thank you Andrey and Bjorn for helping out!
Thanks,
Jeff
next reply other threads:[~2011-08-12 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 21:59 Jeff Chua [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-12 7:01 Jeff Chua
2011-08-12 18:07 ` Bjorn Helgaas
2011-08-11 9:07 Jeff Chua
2011-08-11 21:49 ` Bjorn Helgaas
2011-07-28 5:43 Jeff Chua
2011-08-04 10:56 ` Andrey Panin
2011-08-04 17:39 ` Bjorn Helgaas
[not found] ` <CAAJw_ZvZEn0qVG3JVfEWFQbOSjVUCJhBwQ2Dw5KQyDx2kY4xbA@mail.gmail.com>
2011-08-05 15:20 ` Bjorn Helgaas
[not found] ` <CAAJw_ZvxQQ9-QrSiv9-Y4yCun4W0xvAD3OcdL8gS_hN9FE1rkQ@mail.gmail.com>
2011-08-10 16:46 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1108130553490.22593@boston.corp.fedex.com \
--to=jeff.chua.linux@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=pazke@centrinvest.ru \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®