From owner-freebsd-hackers@freebsd.org Sun Jun 3 07:40:12 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 845E3F77201 for ; Sun, 3 Jun 2018 07:40:12 +0000 (UTC) (envelope-from raul.palomaki@gmail.com) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 DF5E676384 for ; Sun, 3 Jun 2018 07:40:11 +0000 (UTC) (envelope-from raul.palomaki@gmail.com) Received: by mail-lf0-x22e.google.com with SMTP id u4-v6so20572628lff.3 for ; Sun, 03 Jun 2018 00:40:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=8o0Pq3Bq6/hq3EP5xZjiGLPm23xhwaOLHN3/muw+2Uw=; b=LqSK6UaODW/hX1xtVA87dQLBLEbK2z4wTlZP9Dtqvz1rvm2jgJpJ9TlkjO3Ma90p/O sgaPEjMUgZwpcMPANnEttpTu25VAmvlxruwI+5Ffh6kRsnyhYIDfdBVvYaw/F+YDdZtQ vbNG8C7DaAA+T1G8IBFMZUCKfFOr2PTM6JoQE5TL561g3wZzGkaCzt0tmq8clKBRNFu0 68NgW9lLOeHUwGU7Tf3STN725DGFddgnkJlj5XKo9xQvYsg4ND5DTaS3pIm/h+cIrKPg Espa3uKbAQDw4xdl8oKWEcPZ9fBhtPY2wdUQmrhAsPhm/O8oF7DVXE+54HNs1ubS20oG 0Vvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=8o0Pq3Bq6/hq3EP5xZjiGLPm23xhwaOLHN3/muw+2Uw=; b=aiQ1F9ITjYWPUk0OjJGBs5ImjuSR5PsBKn/ZCTmMWPi8ywyAzYpH2g1MpSBbMBxdJZ jJlPYpdnYxiAsSEZcpQvC1nhwN2RBCOnqXEscxidNvPcOI10YsU/mP2ErJGOQYVtbZLO LAOMYaZZRV+rePNhR6cNmZY7vrrC1myoSo3TOw6a7XqAm3bVkLfiA0J8AM48aFdGQ9Qz SgO8uMuybc2a/p9JqnLBEv6oc0Tfs+d9ECWdiGxB8Nz4KEGR484V4jUj10d0ewCceGuz 9Oz9DUSNel9J+KB6GFHCws0zNm9d2kleBT7BjayWEWk8ALI3CuH+s+whiVB1/FNqUfll M8qg== X-Gm-Message-State: APt69E127WNnrWN9K/a7TNGz6+unyDV4PJtf/BV7iOeedtzPt7bQzrzl zqIPQUs/qS5oAtH3lGJNYZKLKseb X-Google-Smtp-Source: ADUXVKLp8aN5ux4FlUIAlfByr51/cpnK5m+bUjI58JR++osPnLjFYow1asqzzDkEXtdTAHx59RdvvA== X-Received: by 2002:a19:7602:: with SMTP id c2-v6mr577495lff.59.1528011610078; Sun, 03 Jun 2018 00:40:10 -0700 (PDT) Received: from tardis (dc376zynwcb3---v08zzy-3.rev.dnainternet.fi. [2001:14ba:15f7:aa01:7210:6fff:fe3e:e528]) by smtp.gmail.com with ESMTPSA id j15-v6sm9143220lji.89.2018.06.03.00.40.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Jun 2018 00:40:09 -0700 (PDT) Sender: Raul Becker Date: Sun, 3 Jun 2018 10:40:19 +0300 From: Raul Becker To: Eric van Gyzen Cc: Warner Losh , "freebsd-hackers@freebsd.org" Subject: Re: Realtek RTS525A SD card reader Message-ID: <20180603074017.jtrn3ykz6ngumdje@tardis> References: <20180401034514.t4idseuyg53gap7g@tardis> <22ca4f05-3e3a-114d-ef95-d974541ee6d8@vangyzen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <22ca4f05-3e3a-114d-ef95-d974541ee6d8@vangyzen.net> User-Agent: NeoMutt/20180323 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 07:40:12 -0000 Hi, yes, thanks for the quick list on what needs to be done! This helped me a ton as well as the arch-handbook. I got the probe to match my device (for now) and attach that initializes the the device as you suggested with freebsd bus resources. It even detects on kldload presence of a sdcard in the slot and reports it in dmesg log. :) But this is still far from anything usable. Just wanted ask if there is any risk that I end up destroying my sd-card device? Like there are some functions in the rtsx driver where the voltages are being changed and also clock hz too. I dont haven't included those functions that do voltage and clock changes yet. -- Raul Becker On Mon, Apr 02, 2018 at 09:39:19AM -0500, Eric van Gyzen wrote: > On 04/01/2018 02:06, Warner Losh wrote: > > The interface you want to look for is the mmcbr_if.m inteface. In sdhci, > > these routines implement the mmc interface: > > sdhci_pci.c: DEVMETHOD(mmcbr_update_ios, sdhci_generic_update_ios), > > sdhci_pci.c: DEVMETHOD(mmcbr_switch_vccq, sdhci_generic_switch_vccq), > > sdhci_pci.c: DEVMETHOD(mmcbr_tune, sdhci_generic_tune), > > sdhci_pci.c: DEVMETHOD(mmcbr_retune, sdhci_generic_retune), > > sdhci_pci.c: DEVMETHOD(mmcbr_request, sdhci_generic_request), > > sdhci_pci.c: DEVMETHOD(mmcbr_get_ro, sdhci_generic_get_ro), > > sdhci_pci.c: DEVMETHOD(mmcbr_acquire_host, sdhci_generic_acquire_host), > > sdhci_pci.c: DEVMETHOD(mmcbr_release_host, sdhci_generic_release_host), > > > > rtsz will almost certainly need it's own versions of these routines (which > > is why I suggest having your own driver will be simpler: otherwise each of > > these routines would be if (rtsz) do_rtsz_stuff(); else do_sdhci_stuff(); > > which won't end well and would be uncomittable to FreeBSD. You can see how > > other chips implement these methods by grepping for them in the tree. You > > may not need a tune/retune if rtsz doesn't support the latest, fastest > > cards, for example. Switch vccq may not be needed either. update_ios will > > be needed, and request is needed. Acquire and release host may be able to > > be done as a dummy routine if there's only one slot. > > > > I know this is a super-quick gloss of what needs to be done. > > This mmc part was helpful, since I know nothing about this interface. > Thanks! > > Eric From owner-freebsd-hackers@freebsd.org Mon Jun 4 22:36:17 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEC46FDD3F1 for ; Mon, 4 Jun 2018 22:36:17 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6866B6AAA5 for ; Mon, 4 Jun 2018 22:36:17 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w54Mc3BW005460 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 4 Jun 2018 22:38:05 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w54Ma8Zl098463 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 4 Jun 2018 15:36:09 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Mon, 4 Jun 2018 15:36:02 -0700 (PDT) From: Don Lewis Subject: defining CPUTYPE when building a custom release To: freebsd-hackers@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 22:36:18 -0000 I'm trying to build a custom 11-STABLE release for a machine that is too wimpy to self-host using the /usr/src/release/release.sh script. The build host is an amd64 machine and the target machine is is in the i386 family. I've set: TARGET=i386 TARGET_ARCH=i386 in the release.conf file. If I don't try to specify a CPUTYPE, I have no problems. But if I add CPUTYPE?=pentium3 to the make.conf file, the release build fails like this: -------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- ===> gnu/lib/libssp/libssp_nonshared (obj,all,install) ===> lib/libcompiler_rt (obj,all,install) ===> gnu/lib/libgcc (obj,all,install) error: unknown target CPU 'pentium3' --- ssp-local.o --- *** [ssp-local.o] Error code 1 This is the same message that I get if I try to compile something on amd64 if I specify -march: %cc -c blah.c -march=pentium3 error: unknown target CPU 'pentium3' but I don't see this when I do the same on an actual i386 machine. I'm assuming it is because pentium3 is not valid amd64 family member. It seems like I should be able to avoid this by telling clang that I want to cross-compile, but clang doesn't seem to like the -arch command line flag: %cc -c blah.c -arch x86 -march=pentium3 cc: warning: argument unused during compilation: '-arch x86' [-Wunused-command-line-argument] error: unknown target CPU 'pentium3' %cc -c blah.c -arch i386 -march=pentium3 cc: warning: argument unused during compilation: '-arch i386' [-Wunused-command-line-argument] error: unknown target CPU 'pentium3' From owner-freebsd-hackers@freebsd.org Tue Jun 5 00:06:22 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85B04FEA060 for ; Tue, 5 Jun 2018 00:06:22 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0DF046F5C0; Tue, 5 Jun 2018 00:06:21 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w54NngTE018862; Mon, 4 Jun 2018 16:49:48 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: In-Reply-To: From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Don Lewis" Subject: Re: defining CPUTYPE when building a custom release Date: Mon, 04 Jun 2018 16:49:48 -0700 Message-Id: <8c9b9690f1080c72ac644bbfbb6c61de@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 00:06:22 -0000 On Mon, 4 Jun 2018 15:36:02 -0700 (PDT) "Don Lewis" = said > I'm trying to build a custom 11-STABLE release for a machine that is too > wimpy to self-host using the /usr/src/release/release=2Esh script=2E The > build host is an amd64 machine and the target machine is is in the i386 > family=2E I've set: > TARGET=3Di386 > TARGET_ARCH=3Di386 > in the release=2Econf file=2E >=20 > If I don't try to specify a CPUTYPE, I have no problems=2E But if I add > CPUTYPE?=3Dpentium3 > to the make=2Econf file, the release build fails like this: >=20 > -------------------------------------------------------------- > >>> stage 4=2E2: building libraries > -------------------------------------------------------------- > =3D=3D=3D> gnu/lib/libssp/libssp_nonshared (obj,all,install) > =3D=3D=3D> lib/libcompiler_rt (obj,all,install) > =3D=3D=3D> gnu/lib/libgcc (obj,all,install) > error: unknown target CPU 'pentium3' > --- ssp-local=2Eo --- > *** [ssp-local=2Eo] Error code 1 >=20 >=20 > This is the same message that I get if I try to compile something on > amd64 if I specify -march: > %cc -c blah=2Ec -march=3Dpentium3 > error: unknown target CPU 'pentium3' > but I don't see this when I do the same on an actual i386 machine=2E I'm > assuming it is because pentium3 is not valid amd64 family member=2E It > seems like I should be able to avoid this by telling clang that I want > to cross-compile, but clang doesn't seem to like the -arch > command line flag: >=20 > %cc -c blah=2Ec -arch x86 -march=3Dpentium3 > cc: warning: argument unused during compilation: '-arch x86' > [-Wunused-command-line-argument] > error: unknown target CPU 'pentium3' > %cc -c blah=2Ec -arch i386 -march=3Dpentium3 > cc: warning: argument unused during compilation: '-arch i386' > [-Wunused-command-line-argument] > error: unknown target CPU 'pentium3' Apologies in advance for even *suggesting*; But the KERNCONF you're working with, originates from, and is within i386/ , not amd64/ =2E Right? --Chris > From owner-freebsd-hackers@freebsd.org Tue Jun 5 00:13:09 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0B0BFEB038 for ; Tue, 5 Jun 2018 00:13:09 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5057E6FBA3 for ; Tue, 5 Jun 2018 00:13:09 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w550EhV4005704 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 5 Jun 2018 00:14:44 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w550Cm8l098794 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2018 17:12:49 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Mon, 4 Jun 2018 17:12:43 -0700 (PDT) From: Don Lewis Subject: Re: defining CPUTYPE when building a custom release To: bsd-lists@BSDforge.com cc: freebsd-hackers@FreeBSD.org In-Reply-To: <8c9b9690f1080c72ac644bbfbb6c61de@udns.ultimatedns.net> Message-ID: References: <8c9b9690f1080c72ac644bbfbb6c61de@udns.ultimatedns.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 00:13:09 -0000 On 4 Jun, Chris H wrote: > On Mon, 4 Jun 2018 15:36:02 -0700 (PDT) "Don Lewis" said > >> I'm trying to build a custom 11-STABLE release for a machine that is too >> wimpy to self-host using the /usr/src/release/release.sh script. The >> build host is an amd64 machine and the target machine is is in the i386 >> family. I've set: >> TARGET=i386 >> TARGET_ARCH=i386 >> in the release.conf file. >> >> If I don't try to specify a CPUTYPE, I have no problems. But if I add >> CPUTYPE?=pentium3 >> to the make.conf file, the release build fails like this: >> >> -------------------------------------------------------------- >> >>> stage 4.2: building libraries >> -------------------------------------------------------------- >> ===> gnu/lib/libssp/libssp_nonshared (obj,all,install) >> ===> lib/libcompiler_rt (obj,all,install) >> ===> gnu/lib/libgcc (obj,all,install) >> error: unknown target CPU 'pentium3' >> --- ssp-local.o --- >> *** [ssp-local.o] Error code 1 > Apologies in advance for even *suggesting*; But the KERNCONF > you're working with, originates from, and is within i386/ , > not amd64/ . Right? Yes. If I don't specify CPUTYPE, I can build a release that installs and runs on the target host. From owner-freebsd-hackers@freebsd.org Tue Jun 5 15:50:52 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4327EFF2B34 for ; Tue, 5 Jun 2018 15:50:52 +0000 (UTC) (envelope-from lakhanshiva@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 7558D807A7; Tue, 5 Jun 2018 15:50:51 +0000 (UTC) (envelope-from lakhanshiva@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id i205-v6so2540494oib.1; Tue, 05 Jun 2018 08:50:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=tCQOPiJjUL8LqOf9/sX/jiK0NE3urixmJNQj5iz9iMc=; b=NnEIcLNLZAiMMUZ7E4EV3rgQtzVOBEztVgc4T/qgxdsGKLVPIJbY58YkqhehHtjj4y zDnpWUHQm0OGWLyA21gBCgVZ7Q2QWXa0dmj2jlMGLPcCajI4gz01UCvwjFHjtmUuaIpp iaVCR9ZxtBN4jFyi7jOWPXj/oW2H3T+TqMstvBQGJjjCiEM2xkcXM7IAE2+Jf7GaiMpG m/8Fa/AQTIaVPuC+ZcDNIJ15PMvCGMp1s2gsOAXY2Y3L1E7Kvkuv5bhnnmB+8v5B7+JW TUosuEhM9WJQDBETHHYpAzJBJI3jcpf57y02441Gi4QbwToKSVHJvqnCWzGGrX9ZlX/g g1ZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=tCQOPiJjUL8LqOf9/sX/jiK0NE3urixmJNQj5iz9iMc=; b=ZKjlTL5oMloMkaig2Kb98qclYSpd0FTjgDLOqpC52Qc4G8VUxLeO7GVfypOZb4sfgX KJZvConiTiMr4ZIbozGSt+Patv1ct9lMFRDKWEMPuOuRyhYPUtvBL4AUl0JSYrcG/UN2 w9YGEMJ49Vgh9tjWJkeGABEf4biCtET/A1et7QFxL1OPErd7nPl2T8L66TZJxtMwdswe fjtBYLq3i64tDZqxDs02iqZSUBkWEk0Dw7wqJM6kE4zyJGhAOpDiKSfdIvnw3e8R1cyT OcDHfE+qdZKE4/mESYD6bd3XRyJdAZdhAiLv25RYdPcyyP/K38XFzbZ4baJAMbRIx8GV J8fw== X-Gm-Message-State: APt69E36pYrQyfLiU+G3luazrwgqlJ85Qh3g+ZzNXS8Ky7MKAnQE1bWE OiLqjoMRgOcTWLKh9JvvRT+gH+HyUuDy0Y9Ijk+MLOZI X-Google-Smtp-Source: ADUXVKJN36osOkDbQWQ/IxuQDyHKqWkYle+sWJYmMxO3TIefxHCvxcBZABLSNPEaM/Q3hxaZ7MBGnkTCJgHDIfKpBeI= X-Received: by 2002:aca:5bc5:: with SMTP id p188-v6mr13870687oib.295.1528213850438; Tue, 05 Jun 2018 08:50:50 -0700 (PDT) MIME-Version: 1.0 From: Lakhan Shiva Date: Tue, 5 Jun 2018 21:20:38 +0530 Message-ID: Subject: cy PCI driver - possible device id's To: freebsd-hackers@freebsd.org Cc: Warner Losh , chuck@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 15:50:52 -0000 Hi All, I am working on converting PCI drivers attachments to be table driven. I have come across the cy (Cyclades Y PCI serial interface driver) - /sys/dev/cy/cy_pci.c. There is no explicit vendor/device table in this. However when we look at the probe function - static int cy_pci_probe(dev) > device_t dev; > { > u_int32_t device_id; > device_id = pci_get_devid(dev); > device_id &= ~0x00060000; > if (device_id != 0x0100120e && device_id != 0x0101120e) > return (ENXIO); > device_set_desc(dev, "Cyclades Cyclom-Y Serial Adapter"); > return (BUS_PROBE_DEFAULT); > } > It makes it evident that it is possible to have the following as the device id's for this Cyclades Cyclom-Y serial Adapter: > 0x0100120e > 0x0102120e > 0x0104120e > 0x0106120e > > 0x0101120e > 0x0103120e > 0x0105120e > 0x0107120e > Can i conclude this or am i missing something here ? Not 100% sure if these are all valid device id's but Math says that these are the possible options. Which all from these could be a practical device id ? As you may infer, i am trying to construct a device id table for the Cyclades PCI driver. Useful Ref: https://www.freebsd.org/cgi/man.cgi?query=cy&sektion=4 Thanks, Lakhan From owner-freebsd-hackers@freebsd.org Tue Jun 5 18:19:38 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF0A0FEF86E for ; Tue, 5 Jun 2018 18:19:37 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 86EC368DD2; Tue, 5 Jun 2018 18:19:37 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 58F1B14891; Tue, 5 Jun 2018 18:19:36 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w55IJaKF032231 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 5 Jun 2018 18:19:36 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w55IJZJA032230; Tue, 5 Jun 2018 18:19:35 GMT (envelope-from phk) To: Lakhan Shiva cc: freebsd-hackers@freebsd.org, chuck@freebsd.org Subject: Re: cy PCI driver - possible device id's In-reply-to: From: "Poul-Henning Kamp" References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <32228.1528222775.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Tue, 05 Jun 2018 18:19:35 +0000 Message-ID: <32229.1528222775@critter.freebsd.dk> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 18:19:38 -0000 -------- In message , Lakhan Shiva writes: >I am working on converting PCI drivers attachments to be table driven. Can we please invent some kind of "typographic" convention which allows these tables to be extracted from the kernel source code, so that we can have an utility which suggests which drivers to load, by consulting such an extracted table ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-hackers@freebsd.org Tue Jun 5 20:17:59 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 156B3FF4D6E for ; Tue, 5 Jun 2018 20:17:59 +0000 (UTC) (envelope-from lakhanshiva@gmail.com) Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (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 89BBC70048; Tue, 5 Jun 2018 20:17:58 +0000 (UTC) (envelope-from lakhanshiva@gmail.com) Received: by mail-oi0-x242.google.com with SMTP id b130-v6so3290827oif.12; Tue, 05 Jun 2018 13:17:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3LKSpuIzTvG29EU53hVIgCb2M3q4viZd0bCS4cLmfaY=; b=RMiHISsm348uY7fciWy+g/pvKxsf9gvKXwoZP1KU1hF9x3KOSttxLKpU/HjOgcRvwr +5o2JmjBWJdS2Jnpqv3QO8GmQm7ZFONGmcNWdsVMLbbh1elVxJdO9UHWkmartRk0XZfU Lh6bZeEWV3pD0eUWXnSDT/ch2PcmDSFCCe7FHm2VpyHaJZnlF8XJGmSHg0ev1GmGiDHj a0OGf/TtyRnGBYxAS2LM/JWpNakERkwKJYt0ShotlAvFYha4XMLlzKi2pa0sBaxquQCW ce33NBXpCYvxNlIYNIGdu/k8PKCBS/xLm7GtACyiuGvXgbZKhPa+CenTFCLDoFUSIYUQ w/qA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3LKSpuIzTvG29EU53hVIgCb2M3q4viZd0bCS4cLmfaY=; b=I4NvoUuLqJtR+lMD0cNehPCu33NptfxyR0eKTk5gFVTOVIL+aCcl0ulmFX+V8/HbKO /o0NfFDwrAXDY9CXhOQKuVSc2BF8n8+4FObf+kHGObt13sYUDF2Nvx7L1XwqNtk8j5g5 60sJF/Bwe7eiDDywpwCZmTFUO604KhHckt8Ed6ffjMB/4pmVuLjXjvXGMkn13KJz9AUy W4iEw4WNFrMjv4hp6xv/BaBKQephzaf4zP1q/VMbqAXg+XrdJW08Fqf+4paRZXkPcRHf 2sLEf5z5fwfxvAmy8EQKaqB2aaazYrRQ33/rTp7ZYz6G60fJ1sTfnNV5wYNyBXwipBIm 67KQ== X-Gm-Message-State: APt69E0LZJYoYWOBLS+VJcRMZBNwWidpN57BtD/nZIwMQ5eFsiMRGQ0m fRwIrvFHK+JNO7QubEFU8/xYniWwSvPaZXUmJSEKcg== X-Google-Smtp-Source: ADUXVKKuemLKls3GdFRMh68VE1i39p9ALr91nI83v5ylxpW4d1XtMzCCxSJ4Bp3IqA5mZrp/Q2LzN2g58nam5rakGu4= X-Received: by 2002:aca:cf84:: with SMTP id f126-v6mr64659oig.131.1528229877826; Tue, 05 Jun 2018 13:17:57 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:4a35:0:0:0:0:0 with HTTP; Tue, 5 Jun 2018 13:17:56 -0700 (PDT) Received: by 2002:a9d:4a35:0:0:0:0:0 with HTTP; Tue, 5 Jun 2018 13:17:56 -0700 (PDT) In-Reply-To: <32229.1528222775@critter.freebsd.dk> References: <32229.1528222775@critter.freebsd.dk> From: Lakhan Shiva Date: Wed, 6 Jun 2018 01:47:56 +0530 Message-ID: Subject: Re: cy PCI driver - possible device id's To: Poul-Henning Kamp Cc: chuck@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 20:17:59 -0000 At present we have devmatch infrastructure, which looks at all unattached devices on the system and compares their plug and play data to that which has been recorded by kldxref in linker hints and suggests modules to load. Now, this work is to support this project achieve this in the case of PCI drivers. Ref: https://wiki.freebsd.org/AutoLoad Thanks, Lakhan On Jun 5, 2018 11:49 PM, "Poul-Henning Kamp" wrote: -------- In message , Lakhan Shiva writes: >I am working on converting PCI drivers attachments to be table driven. Can we please invent some kind of "typographic" convention which allows these tables to be extracted from the kernel source code, so that we can have an utility which suggests which drivers to load, by consulting such an extracted table ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-hackers@freebsd.org Tue Jun 5 20:44:15 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE38CFF5C76 for ; Tue, 5 Jun 2018 20:44:15 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 722DE712CD for ; Tue, 5 Jun 2018 20:44:15 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2E85DFF5C75; Tue, 5 Jun 2018 20:44:15 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C6DBFF5C74 for ; Tue, 5 Jun 2018 20:44:15 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 922FB712CC for ; Tue, 5 Jun 2018 20:44:14 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-wm0-x236.google.com with SMTP id p126-v6so7461703wmb.2 for ; Tue, 05 Jun 2018 13:44:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=QaMQN0duTGnUhDqDgYFAxOe0fvGa/DEJH3VBu1akKbo=; b=gqXDI3+YwcyD5DG33bZW7Kcu2f5vYG8qk1kTo5gkNXGJFubXmEPH5x4EnYKUCPaY2n 3HvbUiJgy/QSima5OCL9neY/fYo8MJq9V4FkmZollTP9Jkfha6HMqPx6e7OilSmXm98A 4/pEXEty3qPNaYsyj1XEQW8bOCmUaJlPLQJY7fw6iRH68gaMxDdM/veYGgNAModQ+GUi 1lq+rnLEvvZkIsM80dWgwGzTrSMyoufzDLGco+uE/afk7YIkERkSno4jiYLXgBdUT7hu op53Rs2Xu5kfzP4ChZVBEVXm7yoYnvUlfJJ1JGe6pS/lq2eC/4PmyovucgwSjSAi1mKW iK0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=QaMQN0duTGnUhDqDgYFAxOe0fvGa/DEJH3VBu1akKbo=; b=HdLIVhiyVmsvP6UDBl4ZySMUdlk+0CU9gpBBOFyyKS6DUxut0DlfpD/5KtyvKtoKwq XMjmUx2INIFqI0ba2dqwqvBhfYiDFFxrEvjcWiO1b0oqBi137DHXSovd/k58IKq/yHUi W7t1J9N+AHSECas3N7fA/fc8WLJYZyg7z/GPOdCiZmNnFBhXcOJnxMak2+FATnFvCDdQ f0rj9fpY5rn8uzl+rU+VhdeHa/P4lmt9DptmpzCFrChUPDVnwbuCeGsxLM7LGg4+KjZt bVDqiEq0HF7ZjVAaFmnDeu9115MRsicGgHAiqNH7t+/8Og+6QCBlHU/I/mrPqSL69VgY dbaQ== X-Gm-Message-State: APt69E2S4LBUGXKV4K7sHRUkHb7w5zpmbokO2UaW4f1I8UVZ4X46sELk hQxqB3NYm9fd2qGYc/UpXymHrV0SOYrj+Sy+lXkBC8W8 X-Google-Smtp-Source: ADUXVKKZ0slqT1VzzJF/DKRWT7Byn8ZmN+/TsUpggqqtlySZOAnK3ReSuyhN4VG1uLbsb4QhvEAeCg1llzL5dMY+QR0= X-Received: by 2002:a50:9090:: with SMTP id c16-v6mr608951eda.310.1528231453449; Tue, 05 Jun 2018 13:44:13 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:b53c:0:0:0:0:0 with HTTP; Tue, 5 Jun 2018 13:44:13 -0700 (PDT) X-Originating-IP: [67.82.37.227] From: Mark Saad Date: Tue, 5 Jun 2018 16:44:13 -0400 Message-ID: Subject: is svnews down or just gone To: hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 20:44:16 -0000 All Does anyone know what happened to http://www.secnetix.de/olli/FreeBSD/svnews/ I enjoyed reading the summary of commits. Is there anything else like this out there ? -- mark saad | nonesuch@longcount.org From owner-freebsd-hackers@freebsd.org Tue Jun 5 20:49:48 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD10BFF5F3D for ; Tue, 5 Jun 2018 20:49:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (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 78E7271662 for ; Tue, 5 Jun 2018 20:49:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x230.google.com with SMTP id g22-v6so5040407iob.7 for ; Tue, 05 Jun 2018 13:49:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A8VbmilXf9MC0tW6mzFpo1QuxqFDRNzN2r/YfIUrvyc=; b=ofVRGJrGCjf6/gH/BpHJ68AoxAcTYd7O3RJ1PLjAHSf6Ski+9K6LuVKlgI+UH5xAxh BsgV8TOzMrOEt6zhTH2uIAtzK666qNJkoptYVREykXqE/zrxNwxtMCP6Y+a6DkdZba7E focrK2+kAEPzXb09Sobwqxf3yWQGSl7sQktc18QKuw52qMNupgEMCDLgrCuCwDa04OB/ yE4SRhE63SitQp7DeEPpRt3acH0/Q/PthXr7fINBz7rFf9cqTnyGbvSUpjy28+We4Vhg /cdYkwGo+TW0+T3hIa00dxDjPJNKXVNijdZFoxEPZ7vlA6XQnTNQ5sdd7jIRPT2amvpm Ndtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A8VbmilXf9MC0tW6mzFpo1QuxqFDRNzN2r/YfIUrvyc=; b=UDQG/Q3KpYn9RKZNViQsW5cvik+JydCm/30b/bmLK48jEioXZ9ZibpM2P1WgQJklpm OOAtSqz3nHo5pZAgHQ3idNwombzj7zpCQAnimxvqqEzczr+QP05sX9Ec441RSZW86IDO XPmAuDSm9MAB81kNcWe9El8SghcS6ukpWovaGTBSY8OTLQ+cvIKNB6j3vYligpkfay8f xPQNfHeZvRMuhWU9YPZkYtG3KEM7v8PMJRSyRHPKDlpMIQHmR8huPPKy2Gp3W6S5xgYc kmRpzslDxOSSgCUpoG2XsuDruHnFDOs11hQZRWHV+nEeTn6Nnd+LAhPZ3bLA6DTFHH8s iUHw== X-Gm-Message-State: APt69E0btqZRJvsqdCF5QE4yZ2frp343hymQUTSHf6gRhwBhhuPpjv4m gzQf4J3HL//BE8PdVz4AQS71shn8NpL1c9DAB0S53w== X-Google-Smtp-Source: ADUXVKKDERdwxORX0xF4hEpDRaa3FhJsbyJVuieu+79jduC1ToIbPMf79J8nFczVvBlQwrUcxH2et3ZJlVepqmIpVbg= X-Received: by 2002:a5e:9817:: with SMTP id s23-v6mr213537ioj.117.1528231786608; Tue, 05 Jun 2018 13:49:46 -0700 (PDT) MIME-Version: 1.0 References: <32229.1528222775@critter.freebsd.dk> In-Reply-To: <32229.1528222775@critter.freebsd.dk> From: Warner Losh Date: Tue, 5 Jun 2018 14:49:34 -0600 Message-ID: Subject: Re: cy PCI driver - possible device id's To: Poul-Henning Kamp Cc: Lakhan Shiva , Chuck Tuffli , freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 20:49:48 -0000 On Tue, Jun 5, 2018, 2:22 PM Poul-Henning Kamp wrote: > -------- > In message < > CAHC0YgfPmPmOQVmHD_uY8d7qHbHLrc439+j34rvLaqo2PMv2VQ@mail.gmail.com>, > Lakhan Shiva writes: > > >I am working on converting PCI drivers attachments to be table driven. > > Can we please invent some kind of "typographic" convention which > allows these tables to be extracted from the kernel source code, > so that we can have an utility which suggests which drivers to > load, by consulting such an extracted table ? > That's exactly what Lakhan is working on. We have the utility (devmatch), just need to mark the drivers. Warner Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Tue Jun 5 20:49:54 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A91F7FF5F58 for ; Tue, 5 Jun 2018 20:49:54 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 44C5B7166B; Tue, 5 Jun 2018 20:49:54 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id E73681484E; Tue, 5 Jun 2018 20:49:47 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w55KnkEf033257 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 5 Jun 2018 20:49:46 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w55KnkNg033256; Tue, 5 Jun 2018 20:49:46 GMT (envelope-from phk) To: cem@freebsd.org cc: "freebsd-hackers@freebsd.org" Subject: Re: cy PCI driver - possible device id's In-reply-to: From: "Poul-Henning Kamp" References: <32229.1528222775@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <33254.1528231786.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Tue, 05 Jun 2018 20:49:46 +0000 Message-ID: <33255.1528231786@critter.freebsd.dk> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 20:49:54 -0000 -------- In message , Conrad Meyer writes: >We already have exactly this =3DE2=3D80=3D94 a precise convention >("MODULE_PNP_INFO") and tool ("kldxref" for extracting the data, and >"devmatch" for suggesting matches), initiated by Warner. This work >has been ongoing, in stops and starts, for years. Lakhan is >converting non-compliant drivers to the convention. Yes, and that's good and great, but it only works if you have the modules installed on the machine to examine. For scenarios like NanoBSD it would be nice if devmatch had a built-in "fall-back" table (created at compile time) to suggest modules not present in the local filesystem. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-hackers@freebsd.org Tue Jun 5 21:00:59 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89E82FF68E5 for ; Tue, 5 Jun 2018 21:00:59 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) (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 F2F4F724D2 for ; Tue, 5 Jun 2018 21:00:58 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f46.google.com with SMTP id 76-v6so5287091itx.4 for ; Tue, 05 Jun 2018 14:00:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=MG4sdivGUL0FICdHi3XRyCvvTP6qHGQKSq3r25RE70A=; b=VHqNx1bGgP1np14/5IoOXf1+NdE+HnC+gYkvumoh/OkRkbRghwZUcvtNvYWpGSt4yM eEafJkgm9uNvxjWTNCUeG1alA7yaTRCvvTs+5gN3RtBtrs8O0n95m1CrJAqJkxLcOl4z PCRJU9Uw7xvGWQlmsnL9LftEaQEo/sDxkct5H/6CNSCJFnM1TZzAVxix4PbxtC0zEaWT UkBL9E/QEQK9pBduQ3getuAZHTYY35Sx1l9dhk8WGGsB6cXiCVWR0fQIWJ98IHLo85Yg GRElY3IDwBIt0dYEJ8ROzeNRqeGpFKIidNMqIikTQqBV9glnvkNABLxeL5PFOfJQqrgn kdeA== X-Gm-Message-State: APt69E2J87SxHV6fKY2ZoQiJn4X8XeYSLfiNuDgIsq9ZyxLEVsJqcYRN nUyJFHj0eB9HHA5nXiJ24r+pRyE8 X-Google-Smtp-Source: ADUXVKKEMJJhV+HwIbix3kDMyZb+tmI3XAq3rtpJrnPEgqByddyaz9Y2JFXfPH7vx5uOfSWDWTkarA== X-Received: by 2002:a24:3a0a:: with SMTP id m10-v6mr828119itm.45.1528230863816; Tue, 05 Jun 2018 13:34:23 -0700 (PDT) Received: from mail-it0-f52.google.com (mail-it0-f52.google.com. [209.85.214.52]) by smtp.gmail.com with ESMTPSA id k130-v6sm1090801itb.0.2018.06.05.13.34.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Jun 2018 13:34:23 -0700 (PDT) Received: by mail-it0-f52.google.com with SMTP id 144-v6so5158501iti.5 for ; Tue, 05 Jun 2018 13:34:23 -0700 (PDT) X-Received: by 2002:a24:5594:: with SMTP id e142-v6mr816192itb.46.1528230863327; Tue, 05 Jun 2018 13:34:23 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:5995:0:0:0:0:0 with HTTP; Tue, 5 Jun 2018 13:34:22 -0700 (PDT) In-Reply-To: <32229.1528222775@critter.freebsd.dk> References: <32229.1528222775@critter.freebsd.dk> From: Conrad Meyer Date: Tue, 5 Jun 2018 13:34:22 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: cy PCI driver - possible device id's To: Poul-Henning Kamp Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 21:00:59 -0000 We already have exactly this =E2=80=94 a precise convention ("MODULE_PNP_INFO") and tool ("kldxref" for extracting the data, and "devmatch" for suggesting matches), initiated by Warner. This work has been ongoing, in stops and starts, for years. Lakhan is converting non-compliant drivers to the convention. Conrad On Tue, Jun 5, 2018 at 11:19 AM, Poul-Henning Kamp wro= te: > -------- > In message , Lakhan Shiva writes: > >>I am working on converting PCI drivers attachments to be table driven. > > Can we please invent some kind of "typographic" convention which > allows these tables to be extracted from the kernel source code, > so that we can have an utility which suggests which drivers to > load, by consulting such an extracted table ? > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetenc= e. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@freebsd.org Tue Jun 5 22:27:45 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9CB1FF9C5D for ; Tue, 5 Jun 2018 22:27:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 E42F17860D for ; Tue, 5 Jun 2018 22:27:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x232.google.com with SMTP id e20-v6so5503981itc.1 for ; Tue, 05 Jun 2018 15:27:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lkLkYA+BRU55agv5CikEwwt3iOqUzDHz2wJJF9GAgKA=; b=a1EOxgg5Igf2H8vG9p9CkXjOu+q3DQl7V1jsT3uAlGTMNP9wnfZ1G+kvoU3mL81iT+ jpum2XIDpMEdUayDTdJExNWZaq6Bb/6MaHH9NMHfZNreX+EtLztRQ/10scdwSp91N8vu zNZLHAs4S5FkrlIgwSDWamZyrDTuHULxtmUSihisCeU1qAlfdKs/Tei7mIf6qO+KTWvH fMVE+ALvIi6xKv01pfXXwjlCFj6h8UL1ZXMe/5cpVRdtjccr9fcJswH5c9Z6A6NeSh3T sNd4JkBc4Ly3lntLEsZ1LtbvrDkIZy4jpz43CtzNAdG59s3XdqzYE2BtFrQ+cLLz6dq8 1TQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lkLkYA+BRU55agv5CikEwwt3iOqUzDHz2wJJF9GAgKA=; b=UBtQBkc9x7rJU8m7y2QLRxzIt62oUoJM69lJ5otDHnWFI0oOhRBi9tY0cN64zU61kG /HRkysS+/Li4ZbdO1roisFiuwjSnRYEvKzN/PLtaadIFeYKU1P/o9b4RwfptaDTp75mG eipYotrSAnEFXeVP37xRbfIrNhUP17+ysCDWLXvvYWgzTzR/tsSLPnyXYLpRRJ0MALCn 32alixrMLPVNoRkxepqoj2slurl6uEJXO4lc7dNSCWZuz17GLO1Hfl6LV497lQhAkNih MJckW5ziUqNqt9s4ZkFRPl9jlLthVSx7B2nqF6CQWwZcHe/AgqgkfFgE1FIelxRellXH Kd3A== X-Gm-Message-State: APt69E1pZgCMt0Fut+R4CdAdEg+IxTVpGCAJeCos+7B/DfUIhQWu2Hbd NgzZCv6QQxthsWyltmiAdUYdV6asuRtPKCSbnppxxQ== X-Google-Smtp-Source: ADUXVKKOxS6bXTq3ad6phubMHk0aqaAa0gC8alhF+PAwMrqrrn8gITcfCbEJuZW/MKs1B8/eSGs9jgwf1HoJyIKhFkU= X-Received: by 2002:a24:7c8d:: with SMTP id a135-v6mr104080itd.73.1528237662235; Tue, 05 Jun 2018 15:27:42 -0700 (PDT) MIME-Version: 1.0 References: <32229.1528222775@critter.freebsd.dk> <33255.1528231786@critter.freebsd.dk> In-Reply-To: <33255.1528231786@critter.freebsd.dk> From: Warner Losh Date: Tue, 5 Jun 2018 16:27:30 -0600 Message-ID: Subject: Re: cy PCI driver - possible device id's To: Poul-Henning Kamp Cc: "Conrad E. Meyer" , FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 22:27:45 -0000 On Tue, Jun 5, 2018, 4:57 PM Poul-Henning Kamp wrote: > -------- > In message < > CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg@mail.gmail.com>, > Conrad Meyer writes: > > >We already have exactly this =E2=80=94 a precise convention > >("MODULE_PNP_INFO") and tool ("kldxref" for extracting the data, and > >"devmatch" for suggesting matches), initiated by Warner. This work > >has been ongoing, in stops and starts, for years. Lakhan is > >converting non-compliant drivers to the convention. > > Yes, and that's good and great, but it only works if you have > the modules installed on the machine to examine. > > For scenarios like NanoBSD it would be nice if devmatch had a > built-in "fall-back" table (created at compile time) to suggest > modules not present in the local filesystem. > Devmatch can operate on an arbitrary loader.hints file. Just do a GENERIC buildkernel, install it somewhere. Loader.hints gets created. Copy that file to the target system and run devmatch... Warner -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Tue Jun 5 22:54:43 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4933FD0BB3 for ; Tue, 5 Jun 2018 22:54:43 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 5AB0B79475; Tue, 5 Jun 2018 22:54:43 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 6B04314846; Tue, 5 Jun 2018 22:54:42 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w55MsfSb035723 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 5 Jun 2018 22:54:41 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w55MseYJ035722; Tue, 5 Jun 2018 22:54:40 GMT (envelope-from phk) To: Warner Losh cc: "Conrad E. Meyer" , FreeBSD Hackers Subject: Re: cy PCI driver - possible device id's In-reply-to: From: "Poul-Henning Kamp" References: <32229.1528222775@critter.freebsd.dk> <33255.1528231786@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <35720.1528239279.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Tue, 05 Jun 2018 22:54:40 +0000 Message-ID: <35721.1528239280@critter.freebsd.dk> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2018 22:54:43 -0000 -------- In message , Warner Losh writes: >Devmatch can operate on an arbitrary loader.hints file. Just do a GENERIC >buildkernel, install it somewhere. Loader.hints gets created. Copy that >file to the target system and run devmatch... Ahh, that was the bit I was missing... Cool and Thanks a LOT for doing this. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-hackers@freebsd.org Wed Jun 6 03:11:54 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3FCBFDE6ED for ; Wed, 6 Jun 2018 03:11:54 +0000 (UTC) (envelope-from waitman@waitman.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 534EF805C9 for ; Wed, 6 Jun 2018 03:11:54 +0000 (UTC) (envelope-from waitman@waitman.net) Received: by mailman.ysv.freebsd.org (Postfix) id 16ABEFDE6EC; Wed, 6 Jun 2018 03:11:54 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05267FDE6EA for ; Wed, 6 Jun 2018 03:11:54 +0000 (UTC) (envelope-from waitman@waitman.net) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9663C805C6 for ; Wed, 6 Jun 2018 03:11:53 +0000 (UTC) (envelope-from waitman@waitman.net) Date: Tue, 05 Jun 2018 23:01:56 -0400 To: "hackers@freebsd.org" From: Waitman Gobble Reply-To: Waitman Gobble Subject: Re: is svnews down or just gone Message-ID: In-Reply-To: References: Feedback-ID: a9EiCCViSiSHQ6Bx5OnM7zSE3j9mdPjjMltovBgA7v_vv_C4nKI9vbMXvmk_xW33cGmibh2zGAa2Co0Llrno4A==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.protonmail.ch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 03:11:54 -0000 =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On June 5, 2018 4:44 PM, Mark Saad wrote: > All >=20 > Does anyone know what happened to http://www.secnetix.de/olli/FreeBSD/svn= ews/ >=20 > I enjoyed reading the summary of commits. Is there anything else like >=20 > this out there ? >=20 >=20 > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= --------------------------- >=20 > mark saad | nonesuch@longcount.org >=20 > freebsd-hackers@freebsd.org mailing list >=20 > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >=20 > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " I do not know the answer, but I put up something similar just now, pulling= from ML posts.=20 https://bsd.do/ I'll tinker with it until it's better.=20 It's displaying HEAD updates only, but probably should cover all active.=20 Waitman Gobble +1 829-914-3703 Sent with ProtonMail Secure Email.=E2=80=8B From owner-freebsd-hackers@freebsd.org Wed Jun 6 08:49:21 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 906B8FED6DB for ; Wed, 6 Jun 2018 08:49:21 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2633F6B07D for ; Wed, 6 Jun 2018 08:49:21 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mailman.ysv.freebsd.org (Postfix) id D4F4CFED6DA; Wed, 6 Jun 2018 08:49:20 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2CD9FED6D9 for ; Wed, 6 Jun 2018 08:49:20 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 48AB46B07C for ; Wed, 6 Jun 2018 08:49:19 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-wm0-x235.google.com with SMTP id p126-v6so9982730wmb.2 for ; Wed, 06 Jun 2018 01:49:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=i8i9YitCaD54nJVakiHM5pHehb2BAXZAKc8iqD4Jzvo=; b=hpP4Ehbpp9woC4mCdWbjnNC9hR1/GJZ0+9EF+5FpHX8ljQDCJly3HDi3/AmteeMNA/ VqFai2pOhlV037SyosuZTHdgyHoGUKadPQ04L4kndpSl5mTxdnbA+s9/T8/9dXXyShQp Kkx/nurWflg6qtJsk2zo1H5Ei3fZ2QDwM/qocgz94yG2moPx34VSJa0IU48RUaRCVBUb hkUZMnD61n/8GIijXp3Gy6ci1+4WTFXw/3G4KZcI3MzGaRX8afonjdVJIGJBuh5B5YqE JnE7P9zX5wxT4bPmm6VnZfKJa+xyf8glAyz715WCAETek4YTfhbpGly664WC2RXiZgZO loxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=i8i9YitCaD54nJVakiHM5pHehb2BAXZAKc8iqD4Jzvo=; b=RhEM9eZmrZWSXqKZe9j7hsU7vkSTNuCMwNo41dIQJnqIWxUg81DVc+aAV4Wk51hvMm IAvEmYXdMw8/lTt0yKHyKoIL1kY9QOQVaaHFJsQBcNDr4Qhtde4J5pExEB4B4yfoavwY A3rnDEL6Ha0Qx1waiwQcDF5GU/DLBSvsuzv6d2fTTz6vY2Qeke10FuzGpeiX3+geeGoT NS1fGV6Cyoa2zX9r5sWWEfO3IoPwJpp1wX7fFa9fDWGzJy+TUcbRjFzFXyi+Am1H5ntd lc+fx007pBabeQ3VExQ533imzUkr4C6Lv9r7eotpSUNaa23BmR9ARpBEKBg6SE2DKmj3 VQmQ== X-Gm-Message-State: APt69E2+dCuC2nsqDAH/z2H4zmqYNTB1e5TJRTGA/UfqQd4vJINsYsTJ xJaO3K9Sfz2ULF/Fs6eJoFzNo0BehejHvj5McKYvd8U2 X-Google-Smtp-Source: ADUXVKKXgQgKKjybg7ZdyJ45QolAqO5fpsRY3AieUqPA1+uRXDcHy7f4vCmSBVP11Yv8EeUzxagqoRb+fBs8H1Bwepg= X-Received: by 2002:a50:88c3:: with SMTP id d61-v6mr2829084edd.122.1528274958122; Wed, 06 Jun 2018 01:49:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:8e0d:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 01:48:47 -0700 (PDT) From: Ed Schouten Date: Wed, 6 Jun 2018 10:48:47 +0200 Message-ID: Subject: Cleanest way of merging back changes to syslogd(8)? To: hackers@freebsd.org Cc: Dave Cottlehuber Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 08:49:21 -0000 Hi there, Some time ago, Dave (cc) asked me whether I'd be interested in merging back the RFC 5424 / ISO 8601 message format changes I made to syslogd(8) to stable/11. Now that stable/11 is open again, I thought I'd go and take a look at doing this. It turns out that merging these changes back is quite challenging. The copy of syslogd(8) in HEAD has diverged very strongly over the last couple of years. There have also been some direct commits to stable/11, so it seems to be (practically) impossible to come up with an invocation of 'svn merge' that does what I expect it would. Because of this, I am considering syncing syslogd(8) between stable/11 and HEAD entirely. More concrete, I want to do this: stable-11 $ cp ../head/usr.sbin/syslogd/* usr.sbin/syslogd/ stable-11 $ svn revert usr.sbin/syslogd/Makefile.depend stable-11 $ svn commit My question is, what's the right way of doing this with SVN (e.g., w.r.t. mergeinfo)? Thanks, -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands From owner-freebsd-hackers@freebsd.org Wed Jun 6 09:21:51 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 704E3FEE4CF for ; Wed, 6 Jun 2018 09:21:51 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 097216BEAE for ; Wed, 6 Jun 2018 09:21:51 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id C1AC3FEE4CE; Wed, 6 Jun 2018 09:21:50 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C404FEE4CD for ; Wed, 6 Jun 2018 09:21:50 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07F0C6BEAB for ; Wed, 6 Jun 2018 09:21:49 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [10.10.154.196] (unknown [185.93.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 7F35843EB7; Wed, 6 Jun 2018 11:21:48 +0200 (CEST) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_99A4AD14-D128-49F2-AB15-B200EA4D5128"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: Cleanest way of merging back changes to syslogd(8)? Date: Wed, 6 Jun 2018 11:21:39 +0200 In-Reply-To: Cc: hackers@freebsd.org, Dave Cottlehuber To: Ed Schouten References: X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 09:21:51 -0000 --Apple-Mail=_99A4AD14-D128-49F2-AB15-B200EA4D5128 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 6 Jun 2018, at 10:48, Ed Schouten wrote: >=20 > Some time ago, Dave (cc) asked me whether I'd be interested in merging > back the RFC 5424 / ISO 8601 message format changes I made to > syslogd(8) to stable/11. Now that stable/11 is open again, I thought > I'd go and take a look at doing this. >=20 > It turns out that merging these changes back is quite challenging. The > copy of syslogd(8) in HEAD has diverged very strongly over the last > couple of years. There have also been some direct commits to > stable/11, so it seems to be (practically) impossible to come up with > an invocation of 'svn merge' that does what I expect it would. >=20 > Because of this, I am considering syncing syslogd(8) between stable/11 > and HEAD entirely. More concrete, I want to do this: >=20 > stable-11 $ cp ../head/usr.sbin/syslogd/* usr.sbin/syslogd/ > stable-11 $ svn revert usr.sbin/syslogd/Makefile.depend > stable-11 $ svn commit >=20 > My question is, what's the right way of doing this with SVN (e.g., > w.r.t. mergeinfo)? Try: svn merge --accept=3Dtheirs-full ^/head/usr.sbin/syslogd = usr.sbin/syslogd which will "overwrite-merge" everything from head's version of syslogd into stable/11's version of it. After that, I am left with the following diff: --- head/usr.sbin/syslogd/syslogd.c 2018-05-13 15:36:09.124043000 = +0000 +++ stable-11/usr.sbin/syslogd/syslogd.c 2018-06-06 = 09:15:14.398673000 +0000 @@ -744,7 +744,7 @@ main(int argc, char *argv[]) fdsrmax =3D sl->sl_socket; } fdsr =3D (fd_set *)calloc(howmany(fdsrmax+1, NFDBITS), - sizeof(*fdsr)); + sizeof(fd_mask)); if (fdsr =3D=3D NULL) errx(1, "calloc fd_set"); @@ -763,7 +763,7 @@ main(int argc, char *argv[]) } bzero(fdsr, howmany(fdsrmax+1, NFDBITS) * - sizeof(*fdsr)); + sizeof(fd_mask)); STAILQ_FOREACH(sl, &shead, next) { if (sl->sl_socket !=3D -1 && sl->sl_recv !=3D = NULL) For some reason, the MFC of r332877 (in r333356) gets overwritten. I guess there is nothing to do but manually correct that again. Oh, and if you want to commit this, you'll have to attempt to defeat the rather silly pre-commit scripts that want to limit subversion merge information. The svn:mergeinfo property on the usr.sbin/syslogd directory will have to be moved to the root of the stable/11 tree, I'm not sure off the top of my head how that should be done. -Dimitry --Apple-Mail=_99A4AD14-D128-49F2-AB15-B200EA4D5128 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWxenowAKCRCwXqMKLiCW o3tZAJ9yXg+D/8ukFoMVepnDdHXaMACr5ACg91NdIX4fQXPUr1nkpT7AK9L0MZc= =2hYO -----END PGP SIGNATURE----- --Apple-Mail=_99A4AD14-D128-49F2-AB15-B200EA4D5128-- From owner-freebsd-hackers@freebsd.org Thu Jun 7 12:03:42 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A83DEFE3DE1 for ; Thu, 7 Jun 2018 12:03:42 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 375DB8D2AE; Thu, 7 Jun 2018 12:03:42 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fQtdk-000B1D-9N; Thu, 07 Jun 2018 15:03:40 +0300 Date: Thu, 7 Jun 2018 15:03:40 +0300 From: Slawa Olhovchenkov To: Poul-Henning Kamp Cc: Lakhan Shiva , chuck@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: cy PCI driver - possible device id's Message-ID: <20180607120340.GF1954@zxy.spb.ru> References: <32229.1528222775@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32229.1528222775@critter.freebsd.dk> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 12:03:42 -0000 On Tue, Jun 05, 2018 at 06:19:35PM +0000, Poul-Henning Kamp wrote: > -------- > In message , Lakhan Shiva writes: > > >I am working on converting PCI drivers attachments to be table driven. > > Can we please invent some kind of "typographic" convention which > allows these tables to be extracted from the kernel source code, > so that we can have an utility which suggests which drivers to > load, by consulting such an extracted table ? ... and from /boot/loader too?.. From owner-freebsd-hackers@freebsd.org Thu Jun 7 21:44:08 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40465FF0830 for ; Thu, 7 Jun 2018 21:44:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 3093380F66 for ; Thu, 7 Jun 2018 21:44:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22a.google.com with SMTP id d185-v6so13600406ioe.0 for ; Thu, 07 Jun 2018 14:44:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=w7ZQ7CIVbKDGFDzGJnXe7Sn97i4QWtW2uThZG/ByyAQ=; b=H774Y0Bc33n8fUgLvKWII1n6jA9gUOfaDZl8r1mA0xBGFmply7xmA3fmdS8rD4c3xb CPt9i/RfAmLEKpA1tuXMOdsHokZg0ehIwJGrCSuNExFtOI/N5hTTONna/hYu1Y9RNE3A L1p1T9k5YwtGhbowpE7niIPR5sbYdLUIoGZOC4ETlhNeZq8mJT1gzxHSupGCXoLgXnVv tVBGcZVCTu/4wGL5EWEnufNNPardduGmsHXgCLLlIoSXXuUFFm0pr9Uoa1Wz/we3qNrL dpc5inBcFFdR1C65qMTkimu6NkLv9mI9bF9GVXZ4c8gg5WLWY+Q8A8vRl5rGlMsO/jb7 RGiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=w7ZQ7CIVbKDGFDzGJnXe7Sn97i4QWtW2uThZG/ByyAQ=; b=gNgIWpJ3CvVtXM80wS4Q/Icr6BAV34+xkk55pezrM+hd48xD6xNoEiL+y0nO3s83ph 2YcJZZmlLp+exQ23ZIOp8N1Ms+nhhFGHOf3+XZMHwRIi+5bX/M2AWBSJVSw3KENu/xEi LtiTaiXfrBevyZJwxLIeuw10dTeWzZWxcBbXn4Y+/iIRVuR7hWgJ8E5NeeBrJUKPvKIN 6v1WJ7eeSuZYB8o7GS0N3IXw5tVErrIujbs2PWxyUimiSgSqrit+2M9J/fLZIxcJWcQo silLuqx96CWE5FgYpwk7cl8HSQgj9cUX0aKdS3LD0toK4AkKZJKAnlXbKqXdRcXuwvpQ xZng== X-Gm-Message-State: APt69E3ffyP3Qzbl5aJIMIgp82zCix4yY6vnoLDQ0NjQTWM2/E/MN2Jk 4hO56D4Vy680rLF+I9k14obWcpgjIgatWu7JGkNrhg== X-Google-Smtp-Source: ADUXVKJTVbWHTm2lRsVrbxOwRJ3tjx7Ak4xMvB5s2UFw7cAERKgYhnDt0aN6WjLC498MRVuTpu8qZIqxwAvCRo0yFe0= X-Received: by 2002:a6b:be01:: with SMTP id o1-v6mr3029866iof.299.1528407846073; Thu, 07 Jun 2018 14:44:06 -0700 (PDT) MIME-Version: 1.0 References: <32229.1528222775@critter.freebsd.dk> <20180607120340.GF1954@zxy.spb.ru> In-Reply-To: <20180607120340.GF1954@zxy.spb.ru> From: Warner Losh Date: Thu, 7 Jun 2018 15:43:54 -0600 Message-ID: Subject: Re: cy PCI driver - possible device id's To: Slawa Olhovchenkov Cc: Poul-Henning Kamp , Lakhan Shiva , chuck@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 21:44:08 -0000 On Thu, Jun 7, 2018, 8:23 AM Slawa Olhovchenkov wrote: > On Tue, Jun 05, 2018 at 06:19:35PM +0000, Poul-Henning Kamp wrote: > > > -------- > > In message < > CAHC0YgfPmPmOQVmHD_uY8d7qHbHLrc439+j34rvLaqo2PMv2VQ@mail.gmail.com>, > Lakhan Shiva writes: > > > > >I am working on converting PCI drivers attachments to be table driven. > > > > Can we please invent some kind of "typographic" convention which > > allows these tables to be extracted from the kernel source code, > > so that we can have an utility which suggests which drivers to > > load, by consulting such an extracted table ? > > ... and from /boot/loader > Yes. Warner >