From owner-freebsd-usb@freebsd.org  Thu Nov 19 08:30:45 2015
Return-Path: <owner-freebsd-usb@freebsd.org>
Delivered-To: freebsd-usb@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44366A33ACD
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Thu, 19 Nov 2015 08:30:45 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (mail.turbocat.net
 [IPv6:2a01:4f8:d16:4514::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E87321647;
 Thu, 19 Nov 2015 08:30:44 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from laptop015.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id B98C91FE023;
 Thu, 19 Nov 2015 09:30:40 +0100 (CET)
Subject: Re: How to access a FTDI usb device with a custom vendor and product
 id's
To: Burton Sampley <bsmply@gmail.com>, Ian Lepore <ian@freebsd.org>
References: <CANV5k3rW62rGoXKD4m5meegEJ04T4b_v=QGCqBV5wuGxZjzCbg@mail.gmail.com>
 <56421DFD.6070503@selasky.org>
 <CANV5k3oRPP_-_SBz2fih0tA12BzoO9Ua+AfJGaE_CCNE3JzpHQ@mail.gmail.com>
 <564222D8.6020900@selasky.org>
 <CANV5k3qzn1UU=qvczGXUr3HQhxf0H8emKSV2XBDD++fDr1yfjg@mail.gmail.com>
 <56422764.4040307@selasky.org>
 <CANV5k3pCx+3za1aPi=u5o36EvicgMgODL=eiTz-_s=nZLqbbAQ@mail.gmail.com>
 <1447277889.91061.22.camel@freebsd.org>
 <CANV5k3omAmBEy00Ny2uhc_NaqnDKbY1knNM8F_wWn2M-o7PHXQ@mail.gmail.com>
 <1447279455.91061.24.camel@freebsd.org>
 <CANV5k3rgow8y=MUjLZW6P38qC6j_jupVsdRzmoZ1WJmL=kP8tQ@mail.gmail.com>
Cc: freebsd-usb@freebsd.org
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <564D8916.9060103@selasky.org>
Date: Thu, 19 Nov 2015 09:32:22 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CANV5k3rgow8y=MUjLZW6P38qC6j_jupVsdRzmoZ1WJmL=kP8tQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2015 08:30:45 -0000

On 11/18/15 20:02, Burton Sampley wrote:
> To All,
>
> A quick update:
>
> I really have no update.  I have been attempting to get to the point where
> I can test the newly built module, but I can not get my system to the point
> where I can try the new module.  I was able to compile it, but when I
> attempted to load the new module, I get the following error:
>
> # /usr/bin/grep uftdi /var/log/messages
> Nov 12 08:14:39 gentoo kernel: KLD uftdi.ko: depends on kernel - not
> available or version mismatch
> #
>
> I then updated my system and source code, now the kernel will not compile.
> I searched and found a few posts on one of the FreeBSD forums, which stated
> the problems might be resolved by "buildworld" first, then "buildkernel",
> "install kernel", reboot single-user and "installworld".  After the latest
> update and reboot, "buildworld" fails.  I don't want to move on to
> "buildkernel" until I can resolve the "buildworld" failure first.
>

Hi,

You only need to build a new kernel.

make -m $PWD/share/mk kernel-toolchain -j8
make -m $PWD/share/mk buildkernel -j8

--HPS