From: Andy Walls <awalls@md.metrocast.net>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: "David Härdeman" <david@hardeman.nu>,
"Jarod Wilson" <jarod@redhat.com>,
"Mauro Carvalho Chehab" <mchehab@redhat.com>,
linux-media@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 3/4] ir-core: move decoding state to ir_raw_event_ctrl
Date: Mon, 21 Jun 2010 07:04:05 -0400 [thread overview]
Message-ID: <1277118245.2230.17.camel@localhost> (raw)
In-Reply-To: <AANLkTikkSIk9XZiuF62YeCmGebrfy8SA9n3J5Agv8LjD@mail.gmail.com>
On Sun, 2010-06-20 at 23:51 -0400, Jarod Wilson wrote:
> On Sun, Jun 20, 2010 at 8:47 PM, Andy Walls <awalls@md.metrocast.net> wrote:
> As for the building your own kernel thing... I've been doing my work
> mainly on a pair of x86_64 systems, one a ThinkPad T61 running Fedora
> 13, and the other an HP xw4400 workstation running RHEL6. In both
> cases, I copied a distro kernel's, config file out of /boot/, and then
> ran make oldconfig over it and build straight from what's in my tree,
> which works well enough on both setups.
I pulled the config out of the kernel*.src.rpm after 'rpmbuild -bp' (I
only saw the configs in /boot after doing that :P ), and then ran 'make
oldconfig'.
The first time around I forgot to do a modules_install and the ext[234]
modules weren't in the initramfs. That made it hard for the kernel to
read the /boot and / filesystems. ;)
After fixing that idiocy, it now hangs in early boot - just a blinking
cursor. I'm speculating it is a problem with support for my old-ish ATI
Radeon Xpress 200 video chipset with a vanilla kernel. I'll work it out
eventually.
> > I'll have time on Thursday night to try again.
>
> No rush yet, we've got a while before the merge window still.
> Christoph (Bartelmus) helped me out with a bunch of ioctl
> documentation this weekend, so I've got that to add to the tree, then
> I think I'll be prepared to resubmit the lirc bits. I'll shoot for
> doing that next weekend, and hopefully, that'll give you a chance to
> try 'em out before then and provide any necessary feedback/fixes/etc.
> (Not that we can't also just fix things up as needed post-merge). I'm
> still up in the air as to what I should work on next... So many lirc
> drivers left to port still... Maybe zilog, maybe streamzap... Maybe
> the MCE IR keyboard...
I've got a PVR-150 and HVR-1600 both with the Zilog Z8's on them. If I
ever get my act together, I'll at least be able to test that and
integrate any changes into the ivtv & cx18 drivers. I've recently seen
users having trouble on IRC, BTW.
Regards,
Andy
next prev parent reply other threads:[~2010-06-21 11:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 21:13 [PATCH 0/4] ir-core sysfs protocol selection simplification David Härdeman
2010-04-24 21:14 ` [PATCH 1/4] ir-core: remove IR_TYPE_PD David Härdeman
2010-04-24 21:14 ` [PATCH 2/4] ir-core: centralize sysfs raw decoder enabling/disabling David Härdeman
2010-05-03 19:49 ` Mauro Carvalho Chehab
2010-06-07 18:48 ` David Härdeman
2010-04-24 21:14 ` [PATCH 3/4] ir-core: move decoding state to ir_raw_event_ctrl David Härdeman
2010-05-03 20:00 ` Mauro Carvalho Chehab
2010-06-07 19:00 ` David Härdeman
2010-06-07 20:15 ` Jarod Wilson
2010-06-08 17:50 ` David Härdeman
2010-06-09 3:46 ` Jarod Wilson
2010-06-09 13:29 ` Jarod Wilson
2010-06-09 17:56 ` David Härdeman
2010-06-09 18:15 ` Jarod Wilson
2010-06-10 1:25 ` Jarod Wilson
2010-06-13 20:29 ` David Härdeman
2010-06-16 20:04 ` Jarod Wilson
2010-06-16 20:41 ` Jarod Wilson
2010-06-17 12:14 ` Andy Walls
2010-06-17 15:11 ` Jarod Wilson
2010-06-21 0:47 ` Andy Walls
2010-06-21 3:51 ` Jarod Wilson
2010-06-21 11:04 ` Andy Walls [this message]
2010-07-06 17:12 ` Jarod Wilson
2010-04-24 21:14 ` [PATCH 4/4] ir-core: remove ir-functions usage from cx231xx David Härdeman
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=1277118245.2230.17.camel@localhost \
--to=awalls@md.metrocast.net \
--cc=david@hardeman.nu \
--cc=jarod@redhat.com \
--cc=jarod@wilsonet.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).