[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK=WgbbV9K-SFbwukDwTAnOBTtwaBUH422Da+CmdvXCN86-aMw@mail.gmail.com>
Date: Tue, 9 Oct 2012 16:38:31 +0200
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Sjur BRENDELAND <sjur.brandeland@...ricsson.com>,
Fengguang Wu <fengguang.wu@...el.com>,
"Linus Walleij (linus.walleij@...aro.org)" <linus.walleij@...aro.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [remoteproc:for-next 6/9] remoteproc_virtio.c:(.text+0x238e7e):
undefined reference to `vring_transport_features'
On Tue, Oct 9, 2012 at 4:26 PM, Dan Carpenter <dan.carpenter@...cle.com> wrote:
> If it already compiles fine on x86 then there is no advantage to
> disabling it.
Not really; that's really a hardware question and not a software one.
There are hardware devices that can go with any platform/architecture,
e.g., WLAN chips. OTOH, there are a lot of hardware devices that are
coupled with certain SoC, e.g. OMAP's remote processors.
What I'm trying to understand is whether the STE modem device belongs
to the former or latter group. It sounds like a modem belongs to the
former group, but if it does belong to the latter, then the building
of its driver should be possible only on the relevant
platforms/architectures.
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists