From owner-freebsd-drivers@FreeBSD.ORG  Wed Mar  4 14:39:57 2015
Return-Path: <owner-freebsd-drivers@FreeBSD.ORG>
Delivered-To: freebsd-drivers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C132A1C0
 for <freebsd-drivers@freebsd.org>; Wed,  4 Mar 2015 14:39:57 +0000 (UTC)
Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com
 [IPv6:2607:f8b0:400d:c00::22b])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 875F7C82
 for <freebsd-drivers@freebsd.org>; Wed,  4 Mar 2015 14:39:57 +0000 (UTC)
Received: by mail-qa0-f43.google.com with SMTP id bm13so33913782qab.2
 for <freebsd-drivers@freebsd.org>; Wed, 04 Mar 2015 06:39:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=ehyGQ2OuESryr3+a6PLRw19sQa3rGp0zk3kvQvKnX9o=;
 b=HaonhiR0oCTRN1FF+MBOigYcIHGm7IpTVrafaer5KOBZj0ei+PKQF4sGpPF8WSVMYN
 mhpBH2YjfYCgFydCaofAuhs6PYMOKx0ntnU2giITnogiBZc5/PuR4eG03j8Gvyqktf78
 2XB7FKn97Ar6BJcxmqjuTJ4bITIjDl3t+suFdMMBzC1SU8IOLK9XZFp/PMN37UlOHZZX
 +uqe8ExS+sklCx+W9SI0rmHpQwokKN8JAjVGHlQRlEcPueUNGK89KefyAKW2bR0e7Kw1
 T2MYsw/FO6N5xVG4s7ittNZNMNzusQQdSb56DejokfZxFFJzL5YkrQNb0zLt24MZCS1L
 pEEg==
MIME-Version: 1.0
X-Received: by 10.140.234.130 with SMTP id f124mr6419092qhc.36.1425479996728; 
 Wed, 04 Mar 2015 06:39:56 -0800 (PST)
Received: by 10.140.37.82 with HTTP; Wed, 4 Mar 2015 06:39:56 -0800 (PST)
Date: Wed, 4 Mar 2015 11:39:56 -0300
Message-ID: <CADLKG02uCGKARNDTetHjf-TM_bp_rDD43W9H=ARgRhE4jeDZwA@mail.gmail.com>
Subject: call identify, probe and attach on run time?
From: =?UTF-8?Q?Mat=C3=ADas_Perret_Cantoni?= <perretcantonim@gmail.com>
To: freebsd-drivers@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-drivers@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Writing device drivers for FreeBSD <freebsd-drivers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-drivers>, 
 <mailto:freebsd-drivers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-drivers/>
List-Post: <mailto:freebsd-drivers@freebsd.org>
List-Help: <mailto:freebsd-drivers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-drivers>,
 <mailto:freebsd-drivers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2015 14:39:57 -0000

Hello! I'm a newbie at freeBSD and at the development of newbus drivers, so
excuse me if this is too silly:

I'm running FreeBSD on the Zedboard, an arm based board, and I wrote a
simple newbus driver for reading and writing a specific I/O port (It is
basically a simplified copy of the Warner Losh example driver for the
iOpener Led)

I successfully load my driver:

# kldload ./simple_d.ko
#

But after doing this I can't find the new node neither under /dev nor with
devinfo(8). I assume that the identify, probe and attach functions hasn't
been called. Is this correct?

So is there any way of doing this at run time? I mean NOT during
auto-configuration.

If I can only do it on boot time ...
... should I add a node at the Flattened Device Tree?
... should I place the driver in some specific directory?
... should I re-compile the kernel with the new driver included?


Thank you!
Regards,
Matias.-