Hi.
On 2023/12/31 7:44, Taylor R Campbell wrote:
> I propose to deprecate the kmem(9) interface and go back to the
> malloc(9) interface.
>
>
> 1. The main difference is that the malloc(9) interface enables
>attribution of memory usage: how many bytes have been used for this
>purpose vs
On 2023/03/09 19:21, Robert Elz wrote:
> Date:Thu, 9 Mar 2023 16:21:53 +0900
> From: Masanobu SAITOH
> Message-ID: <38ae66bd-1b37-c0ef-5a43-52e0c0a2a...@execsw.org>
>
> | Alder Lake-N? 4 E-cores share one microcode image. I have i7-12700
Hello, all.
On 2023/03/05 11:01, Robert Elz wrote:
> Date:Fri, 3 Mar 2023 21:46:22 -0800
> From:"William 'Cryo' Coldwell"
> Message-ID: <7ce92f54-3746-4106-bd63-16e5e4cbc...@netbsd.org>
>
> | To throw some extra fun mixture into this discussion: As of 5.19
> | L
Hello.
I'm sorry for the late of this reply. I was busy for a few weeks.
On 2023/03/03 6:59, Robert Elz wrote:
> This message is about a proposed userland modification, but it seems
> more kernelish to me, hence I am asking here on tech-kern, rather than
> on tech-userlevel
>
> When my system bo
Hi.
On 2022/09/18 2:55, John Klos wrote:
> Hi,
>
> Here's a nice issue :)
>
> Plug in ure* USB ethernet to amd64 machine running NetBSD-current (9.99.99,
> 22-August-2022):
>
> [ 1791670.446266] ure0 at uhub8 port 4
> [ 1791670.446266] ure0: Realtek (0x0bda) USB 10/100/1000 LAN (0x8153), rev
On 2022/09/14 19:01, Edgar Fuß wrote:
>> I need to build a new install image (since I have no discs).
> I applied your fix to -8 and the panic disappeared.
> Thanks for the quick fix. Maybe it should be pulled up?
I'll send pullup requests.
--
---
This should be fixed by mfii.c rev. 1.26. Please update it and retry.
On 2022/09/14 6:14, Edgar Fuß wrote:
> I get a panic on shutdown:
>
> netbsd:sysmon_envsys_unregister+0x128:cmpq0(%rdx),%r12
> sysmon_envsys_unregister
> mfii_detach
> config_detach
> config_detach_all
> cpu_reboot
Hi.
On 2022/08/08 19:41, Edgar Fuß wrote:
> Thanks for your answers.
>
>> Some people reported that kern/56669 (and perhaps kern/55192) still exist
>> on some systems :-(
> Hm.
>
>> bioctl mfi(i)X show
> Ah, thanks.
> What do I do in case a drive fails? Will adding a hot spare automagically
>
On 2022/08/08 18:37, Edgar Fuß wrote:
> I'm unsure whether this is the right list, is port-amd64 more appropriate?
>
> Does anyone use a Dell PERC H730P or similar RAID controller in RAID mode?
It seems PERC H730P's device ID is 0x005d.
https://pci-ids.ucw.cz/read/PC/1000/005d
It's t
On 2022/06/23 18:33, Edgar Fuß wrote:
>> I committed the change yesterday.
> I don't get what the #if defined(__LP64__) && 0 is for.
It's just to make the same line as of bus_space_write_8().
I don't know why it's "&& 0"ed.
---
static void
mfii_start(struct mfii_softc *sc, struct mfii_c
Hi.
On 2022/06/02 19:08, BERTRAND Joël wrote:
> Hello,
>
> In a recent mail (if_wm.c workqueue), I have seen that it is possible
> to activate workqueue on all ethernet devices contained in my server:
>
> [ 1.002997] wm0 at pci2 dev 0 function 0: I350 Gigabit Network
> Connection
On 2022/06/22 4:55, c...@sdf.org wrote:
> Hello Masa -
Hi, Stephen.
> I was able to apply your patch to the 9.2 tree and built a kernel and
> pxebooted it. Unfortunately the status now looks like this:
>
> mfii0 at pci5 dev 0 function 0mfii0: firmware fault
>
> https://sdf.org/eu (full boo
I have 9272-8i and it have been working well on netbsd-9 since several
weeks ago.
> mfii0 at pci1 dev 0 function 0: "LSI MegaRAID SAS 9272-8i", firmware
> 23.34.0-0019, 512MB cache
> mfii0: interrupting at ioapic0 pin 16
Could you all who have problem with mfii(4) test with the following diff?
Hi.
On 2020/06/10 4:37, Joerg Sonnenberger wrote:
> On Tue, Jun 09, 2020 at 05:16:27PM +, Taylor R Campbell wrote:
>> It's great to see improvements to our calibration of the TSC (and I
>> tend to agree that cpu_counter should be serializing, so that, e.g.,
>> cpu_counter(); ...; cpu_counter()
On 2020/01/06 17:06, Emmanuel Dreyfus wrote:
> On Thu, Jan 02, 2020 at 03:55:31PM +, Emmanuel Dreyfus wrote:
>> And indeed, studying the crash in ddb shows it happens when
>> accessing a physical address that is excluded by x86_fake_clusters()
>> but included by EFI memory map.
>
> I think th
On 2019/12/02 15:48, s ymgch wrote:
> I'm re-sending the last mail because I forgot to set ML addresses to
> destination e-mail address.
>
> 2019年12月2日(月) 12:53 s ymgch :
>>
>> 2019年12月1日(日) 2:08 Taylor R Campbell :
> Are you using BUS_SPACE_MAP_PREFETCHABLE?
No, the driver does not
On 2019/01/28 20:57, Jonathan A. Kollasch wrote:
On Mon, Jan 28, 2019 at 07:34:29PM +0900, Masanobu SAITOH wrote:
Hi.
I'm now working to modify PCI bridge stuff. I'd like to do the following
two modifications:
0) ppbreg.h definitions
All of PCI configuration space&
On 2019/02/28 16:54, matthew green wrote:
Iain Hibbert writes:
On Thu, 28 Feb 2019, Masanobu SAITOH wrote:
I'd like to get new number for new ioctl. How should I find unused number
for it? I'm going to add new SIOCXXX. It may not enough to grep sys/net/*.h,
so I made usr.bin/kdu
Hi.
This might be FAQ...
I'd like to get new number for new ioctl. How should I find unused number
for it? I'm going to add new SIOCXXX. It may not enough to grep sys/net/*.h,
so I made usr.bin/kdump-ioctl.c and did
grep \'i kdump-ioctl.c | sort -n -k 5,5 | uniq | column -t
I think
Hi, all.
I'm sorry for being little late.
On 2019/01/31 14:21, Rin Okuyama wrote:
On 2019/01/30 23:47, Jason Thorpe wrote:
On Jan 30, 2019, at 3:29 PM, Robert Elz wrote:
| Yes, I think something like:
|
| size_t mbuf_cluster_size_for_size(size_t desired_size);
whatever the name, is
Hi.
I'm now working to modify PCI bridge stuff. I'd like to do the following
two modifications:
0) ppbreg.h definitions
All of PCI configuration space's register definitions are in pcireg.h
The ppbreg.h file also defines the same config registers. I think it's
good to remove ppbr
On 2018/12/04 13:53, Jason Thorpe wrote:
I'm working on an application where I need some additional run-time flexibility
PLEASE!
sys/dev/ic/com.c has some compile time #ifdef 's and it cause bad
effect to usb serial and/or puc com devices.
in how the "com" driver register map is setup. COM_
On 2018/12/05 4:53, Jaromír Doleček wrote:
I've now disabled MSI-X for ahcisata(4), need to figure what needs to
be setup there.
Le lun. 3 déc. 2018 à 22:41, Jared McNeill a écrit :
IIUC we don't actually have confirmation that ThunderX AHCI works yet..
Nick is having issues with his board.
On 2018/12/04 16:44, Masanobu SAITOH wrote:
On 2018/12/04 4:55, Jaromír Doleček wrote:
Le lun. 3 déc. 2018 à 12:09, Masanobu SAITOH a écrit :
C3000's AHCI has multi-vector MSI-X table and it doesn't work since
Nobember 20th...
Can you try if by chance this code adapted nvme(
On 2018/12/04 4:55, Jaromír Doleček wrote:
Le lun. 3 déc. 2018 à 12:09, Masanobu SAITOH a écrit :
C3000's AHCI has multi-vector MSI-X table and it doesn't work since
Nobember 20th...
Can you try if by chance this code adapted nvme(4) changes anything on
your system?
http://www.
On 2018/12/01 5:27, Jared McNeill wrote:
On Fri, 30 Nov 2018, Martin Husemann wrote:
On Fri, Nov 30, 2018 at 02:22:37PM -0400, Jared McNeill wrote:
The driver can call pci_intr_type on the handle returned by pci_intr_alloc
to see what kind of interrupt (INTx/MSI/MSI-X) was negotiated.
Yeah,
Hi.
While I've been working for suspend/resume, I've noticed that some devices
are reported "WARNING: power management not supported" in config_attach_loc()
even though the driver has pmf_device_register() in it. The reason is that
pmf_device_register is deferred by config_interrupts(). It's no
On 2018/08/30 20:54, D'Arcy Cain wrote:
My latest build of NetBSD 8 results in a kernel size of 24,964,488
bytes. Not sure if "kernel" is really the right term any more. :-)
I have installed it on all of my servers except for one. It is a HP
ProLiant DL160se G6. The failure is something like
On 2018/04/21 3:55, Mouse wrote:
I'm trying to write some bare-metal code (no OS) for a chip that
appears to be supported by if_wm.c, but for which the manufacturer's
documentation PDF is cripplingly broken, leading to my reading over
that file, trying to use it as hardware documentation of a sor
On 2018/01/15 18:12, Emmanuel Dreyfus wrote:
On Mon, Jan 15, 2018 at 05:34:18PM +0900, Masanobu SAITOH wrote:
cpu0: MSR_IA32_ARCH_CAPABILITIES=0x1
I've not written this bit by myself.
Where can this be readen without your patch?
In cpu_ucode_intel.c::cpu_ucode_intel_
On 2018/01/15 17:42, Masanobu SAITOH wrote:
On 2018/01/15 17:34, Masanobu SAITOH wrote:
On 2018/01/15 3:42, Dave Huang wrote:
On Jan 13, 2018, at 22:20, Emmanuel Dreyfus mailto:m...@netbsd.org>> wrote:
John Klos mailto:j...@ziaspace.com>> wrote:
FWIW, Intel updated their microc
On 2018/01/15 17:34, Masanobu SAITOH wrote:
On 2018/01/15 3:42, Dave Huang wrote:
On Jan 13, 2018, at 22:20, Emmanuel Dreyfus mailto:m...@netbsd.org>> wrote:
John Klos mailto:j...@ziaspace.com>> wrote:
FWIW, Intel updated their microcode on 8-Jan-2018:
https://downloadcent
On 2018/01/15 3:42, Dave Huang wrote:
On Jan 13, 2018, at 22:20, Emmanuel Dreyfus mailto:m...@netbsd.org>> wrote:
John Klos mailto:j...@ziaspace.com>> wrote:
FWIW, Intel updated their microcode on 8-Jan-2018:
https://downloadcenter.intel.com/download/27431/
I can't find any documentation wh
On 2017/12/27 1:37, Martin Husemann wrote:
On Tue, Dec 26, 2017 at 07:05:38PM +0900, Masanobu SAITOH wrote:
so checking mp_online is the best, right?
I wonder if we should additionaly check for ncpu >= 2 (or ncpuonline >=
2), but that is probably overoptimization.
I think doing optimi
On 2017/12/26 11:59, Masanobu SAITOH wrote:
On 2017/12/25 20:26, Martin Husemann wrote:
On Mon, Dec 25, 2017 at 03:42:06PM +0900, Masanobu SAITOH wrote:
Is this intended behavior? Is it possible to use xcall while
cold==1?
Cold is (as you noted) not the right condition (but pretty close
On 2017/12/25 20:26, Martin Husemann wrote:
On Mon, Dec 25, 2017 at 03:42:06PM +0900, Masanobu SAITOH wrote:
Is this intended behavior? Is it possible to use xcall while
cold==1?
Cold is (as you noted) not the right condition (but pretty close).
Xcalls don't really make any sense b
Hi.
While debugging PR#52820 ("boot -1" panics on systems with ixgX interfaces),
I've noticed that xcall doesn't work while cold == 1.
When I added softint_disestablish() near the end of the ixgbe_attach().
The following panic occured:
panic: kernel diagnostic assertion "xc->xc_donep < xc->
On 2017/11/21 15:35, Masanobu SAITOH wrote:
On 2017/11/20 17:28, Masanobu SAITOH wrote:
On 2017/11/17 18:42, 6b...@6bone.informatik.uni-leipzig.de wrote:
On Thu, 16 Nov 2017, Masanobu SAITOH wrote:
Hi, all.
Some device drivers now allocate a lot of softints.
See:
http://mail
On 2017/11/21 17:03, matthew green wrote:
It'll take a little time to write this change. And, it's low level
and important code, so it will take a time to test the stability
before sending pullup request. So,
0) Apply the following change to -current.
Inde
On 2017/11/20 17:28, Masanobu SAITOH wrote:
On 2017/11/17 18:42, 6b...@6bone.informatik.uni-leipzig.de wrote:
On Thu, 16 Nov 2017, Masanobu SAITOH wrote:
Hi, all.
Some device drivers now allocate a lot of softints.
See:
http://mail-index.netbsd.org/current-users/2017/11/09/msg032581
can't this be fixed by making it dynamic?
It's not easy because the return value of softint_establish() is
made from this area's address. As you know, the value is keep by each driver.
I'm sorry. I misread kern_softint.c. The return value is not directly point to
the area, but it's offse
On 2017/11/17 18:42, 6b...@6bone.informatik.uni-leipzig.de wrote:
On Thu, 16 Nov 2017, Masanobu SAITOH wrote:
Hi, all.
Some device drivers now allocate a lot of softints.
See:
http://mail-index.netbsd.org/current-users/2017/11/09/msg032581.html
To avoid this panic, I wrote the following
Hi, all.
On 2017/11/17 15:35, Masanobu SAITOH wrote:
Hi, mrg.
On 2017/11/17 5:05, matthew green wrote:
Masanobu SAITOH writes:
Hi, all.
Some device drivers now allocate a lot of softints.
See:
http://mail-index.netbsd.org/current-users/2017/11/09/msg032581.html
To avoid this
nly
relevant during boot anyway,
As I wrote, it's incorrect because ifconfig xxxN create allocates softint.
so it's not very helpful.
Jaromir
2017-11-16 21:05 GMT+01:00 matthew green mailto:m...@eterna.com.au>>:
Masanobu SAITOH writes:
> Hi, all.
>
Hi, mrg.
On 2017/11/17 5:05, matthew green wrote:
Masanobu SAITOH writes:
Hi, all.
Some device drivers now allocate a lot of softints.
See:
http://mail-index.netbsd.org/current-users/2017/11/09/msg032581.html
To avoid this panic, I wrote the following patch:
http
Hi, all.
Some device drivers now allocate a lot of softints.
See:
http://mail-index.netbsd.org/current-users/2017/11/09/msg032581.html
To avoid this panic, I wrote the following patch:
http://www.netbsd.org/~msaitoh/softint-20171116-0.dif
Summary:
- Increase the def
Hi, Rocky.
On 2017/05/18 18:21, Rocky Hotas wrote:
Hi Masanobu and hi all!
After the discussion on this thread,
http://mail-index.netbsd.org/netbsd-users/2017/02/01/msg019280.html
I'm trying to apply this patch
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/ppb.c.diff?r1=1.35&r2=1.3
On 2017/03/24 8:13, Michael wrote:
Hello,
On Wed, 22 Mar 2017 16:35:21 +0900
Masanobu SAITOH wrote:
A) modify pci_mapreg_map(). Stop setting BUS_SPACE_MAP_PREFETCHABLE
by defalut when prefetchable bit is set. If a driver really know
the whole area of the BAR is prefetchable, set
Hi.
As some people know, our pci(9) had a problem with devices that
a BAR has prefetchable bit. It makes unexpected behavior on read/
write. To avoid this problem some device drivers have common hack.
Instead of using pci_mapreg_map(), it uses pci_mapreg_info() and
pass the result to bus_space_
Hello, all.
Thanks all people who replied to my proposal. One of my fault is that
I didn't show any example code. I made patches. As jnemeth@ said, my
change is straightforward and the change should not cause any catastrophic
problem.
In my last mail,
c) We can add the code to fallbac
On 2016/07/15 18:52, Martin Husemann wrote:
On Fri, Jul 15, 2016 at 06:30:23PM +0900, Masanobu SAITOH wrote:
Or enclose with #ifdef DIAGNOSTIC?
Assuming we do not use aprint_error when there is no "error",
Some drivers use aprint_error() to warn a problem and continue
attaching
On 2016/07/15 16:45, Masanobu SAITOH wrote:
Hi.
aprint_error*() increments aprint_error_count.
At the end of config_finalize():
KERNEL_UNLOCK_ONE(NULL);
errcnt = aprint_get_error_count();
if ((boothowto & (AB_QUIET|AB_SILENT)) != 0 &&
(boothowto &
Hi.
aprint_error*() increments aprint_error_count.
At the end of config_finalize():
KERNEL_UNLOCK_ONE(NULL);
errcnt = aprint_get_error_count();
if ((boothowto & (AB_QUIET|AB_SILENT)) != 0 &&
(boothowto & AB_VERBOSE) == 0) {
mutex_enter(&conf
On 2016/07/05 1:40, Edgar Fuß wrote:
wm0 seem to fail permanently whenever it's interrupts aren't serviced
for some time.
For which value of ``permanently''? Do I need to buy a new NIC [Fe]?
Does something like ifconfig up/down help?
The mpt recovery code (like e.g. the wd recovery code) can k
Hi, all.
As you know, the return value of device driver's attach function is void.
I've thought that we should change it to int for many years. I believe I'm
not the only person.
xxx_attach() may fail the following cases:
got unexpected behavior.
resource allocation error.
On 2015/10/01 22:59, Christos Zoulas wrote:
> On Oct 1, 7:21pm, msai...@execsw.org (Masanobu SAITOH) wrote:
> -- Subject: Re: PCI extended configuration support
>
> | pci_conf_read() have to call chip dependent function. I think
> | it's not good idea to call chip d
On 2015/09/28 22:41, Christos Zoulas wrote:
> On Sep 28, 7:51pm, msai...@execsw.org (Masanobu SAITOH) wrote:
> -- Subject: Re: PCI extended configuration support
>
> | On 2015/09/27 11:03, Christos Zoulas wrote:
> | > In article <5604d1be.3080...@execsw.org>,
>
On 2015/09/27 11:03, Christos Zoulas wrote:
> In article <5604d1be.3080...@execsw.org>,
> Masanobu SAITOH wrote:
>> On 2015/09/11 19:44, Masanobu SAITOH wrote:
>>
>> More machines support the extended configuration area than before.
>>
>> Is it OK t
On 2015/09/11 19:44, Masanobu SAITOH wrote:
Hi, Jonathan.
On 2015/09/09 23:02, Jonathan A. Kollasch wrote:
On Tue, Sep 08, 2015 at 12:58:31PM +0900, MAEKAWA Masahide wrote:
On 2015/09/08 0:59, Jonathan A. Kollasch wrote:
- abuse of the pcitag_t (I have patches that fix this.)
Your
Hi, Jonathan.
On 2015/09/09 23:02, Jonathan A. Kollasch wrote:
On Tue, Sep 08, 2015 at 12:58:31PM +0900, MAEKAWA Masahide wrote:
On 2015/09/08 0:59, Jonathan A. Kollasch wrote:
- abuse of the pcitag_t (I have patches that fix this.)
Your patches? Where? your local?
Attached. This has
On 2015/09/10 17:24, Martin Husemann wrote:
On Thu, Sep 10, 2015 at 10:21:01AM +0200, Marc Balmer wrote:
I used to start a netbsd-6 machine by sending Wake-on-LAN frames wo it.
After upgrading that machine to netbsd-7, it ignores these WoL packages and
does not start.
Its an i386 with bge(4) i
Hi, all.
nonaka@ wrote code to access PCI extended configuration area.
Currently, the diff supoorts only on x86.
http://ftp.netbsd.org/pub/NetBSD/misc/nonaka/tmp/nbsd-pci-extconf-support.diff
Is it OK to commit?
--
---
SAIT
Hi, Bert.
On 2015/08/18 4:09, Bert Kiers wrote:
On Mon, Aug 17, 2015 at 05:38:09PM +0200, Bert Kiers wrote:
# uname -a
NetBSD 7.99.21 NetBSD 7.99.21 (GENERIC) #0: Mon Aug 17 17:13:23 CEST 2015
ki...@shell.boppelans.net:/tmp/obj25032/sys/arch/amd64/compile/GENERIC amd64
# dmesg|grep ixv
ixv
On 2015/08/13 18:14, Bert Kiers wrote:
On Thu, Aug 13, 2015 at 02:16:27PM +0900, Masanobu SAITOH wrote:
Hi, all.
I've commited change to support ixv(4), Intel 10G Ethernet's virtual
function. The reason why this driver had not been compilable is that
it supports MSI-X only.
Cu
Hi, all.
I've commited change to support ixv(4), Intel 10G Ethernet's virtual
function. The reason why this driver had not been compilable is that
it supports MSI-X only.
Currently, I have not environment to test this driver. Could some
people who are familiar with it test with the latest -cur
Hi, Christos.
On 2015/08/07 18:53, Christos Zoulas wrote:
> In article <55c349bf.2000...@execsw.org>,
> Masanobu SAITOH wrote:
>> Hi, all.
>>
>> Currently, pci_msi_count() and pci_msix_count() take one
>> pci_attach_args argument.
>> These functions may
Hi, all.
Currently, pci_msi_count() and pci_msix_count() take one pci_attach_args
argument.
These functions may be used in other than attach function. So, it might be
better to use pci_chipset_tag_t and pcitag_t.
Is the following diff better than current specification?
Index: share/man/man9
On 2015/02/17 19:06, 6b...@6bone.informatik.uni-leipzig.de wrote:
On Wed, 4 Feb 2015, Christos Zoulas wrote:
...
christos
I have tested NetBSD 7.99.x
The problem is now solved. The PR can be closed.
Regards
Uwe
Thanks. I'll send the pullup requet to netbsd-7.
--
On 2015/01/29 16:31, Masanobu SAITOH wrote:
(snip)
Some of Ethernet drivers avoid using splnet()/splx() and use mutexes.
wm, bnx, ixg, powerpc/booke/dev/pq3etsec.c and others. I think it's better
to know the common solution and puse the way.
I wrote the following page:
On 2015/01/29 20:39, Edgar Fuß wrote:
EF> I even get a message "Please update the Bootagent", whatever that means,
EF> exactly.
MS> That code is a workaround code for old boot rom which doesn't release
MS> semaphore.
Ah, thanks. Do you happen to know how to perform that update using NetBSD?
boo
On 2015/02/04 14:08, Christos Zoulas wrote:
> On Feb 4, 1:49pm, msai...@execsw.org (Masanobu SAITOH) wrote:
> -- Subject: Re: PR/49328 CVS commit: src/sys/dev/pci/ixgbe
>
> | Hi, all.
> |
> | I fixed and committed some smallproblem to -current.
> |
> | The rest
Hi, all.
I fixed and committed some smallproblem to -current.
The rest is:
- Revert ixgbe_netbsd.c rev. 1.2
- make CORE_LOCK adaptive
- Release spin lock while reinitializing the jumb buffer structure.
Is it OK to commit?
Index: ixgbe.c
Hi.
Uwe Toenjes found a bug in ixg(4). See:
http://mail-index.netbsd.org/current-users/2014/10/11/msg025932.html
Then, PR#49328 was submitted by him.
http://gnats.netbsd.org/49328
This problem is can be reproduced when
LOCKDEBUG is defined
ifconfig ixg0 up
On 2015/01/29 3:16, Edgar Fuß wrote:
Could you try the following patch?
Ah, looks much better, thanks!
I haven't tried to actually use the interface, though.
I even get a message "Please update the Bootagent", whatever that means,
exactly.
That code is a workaround code for old boot rom whi
Hi, all
On 2015/01/12 22:38, Edgar Fuß wrote:
I have a similar problem with a "IBM PRO/1000 PT Dual Port Server Adapter Low
Profile - 39Y6128" (in a HP MicroServer) that was at least recognized with 6, but on
7, I get:
wm0 at pci2 dev 0 function 0: Intel PRO/1000 PT (82571EB) (rev. 0x06)
wm0
On 2014/09/04 11:24, Masanobu SAITOH wrote:
On 2014/09/04 0:40, Emmanuel Dreyfus wrote:
On Wed, Sep 03, 2014 at 04:11:29PM +0200, Bert Kiers wrote:
NetBSD 6.1 says:
vendor 0x8086 product 0x1528 (ethernet network, revision 0x01) at pci1 dev 0
function 0 not configured
In src/sys/dev/pci
On 2014/09/04 0:40, Emmanuel Dreyfus wrote:
On Wed, Sep 03, 2014 at 04:11:29PM +0200, Bert Kiers wrote:
NetBSD 6.1 says:
vendor 0x8086 product 0x1528 (ethernet network, revision 0x01) at pci1 dev 0
function 0 not configured
In src/sys/dev/pci/ixgbe/ we know about producct Id 0x1529 and 0x152A
Hi, Emmanuel.
On 2014/09/01 11:10, Emmanuel Dreyfus wrote:
> Terry Moore wrote:
>
>> Since you did a dword read, the extra 0x9 is the device status register.
>> This makes me suspicious as the device status register is claiming that you
>> have "unsupported request detected)" [bit 3] and "co
On 2014/07/24 14:17, Masanobu SAITOH wrote:
On 2014/07/24 14:16, Masanobu SAITOH wrote:
On 2014/07/24 1:31, Manuel Bouyer wrote:
On Wed, Jul 23, 2014 at 08:46:34AM -0400, Thor Lancelot Simon wrote:
I just ordered a Supermicro low-power rackmount x86 machine which -- I
discovered after
On 2014/07/24 14:16, Masanobu SAITOH wrote:
On 2014/07/24 1:31, Manuel Bouyer wrote:
On Wed, Jul 23, 2014 at 08:46:34AM -0400, Thor Lancelot Simon wrote:
I just ordered a Supermicro low-power rackmount x86 machine which -- I
discovered after ordering it -- uses a Marvell 88SE9230 as a SATA
On 2014/07/24 1:31, Manuel Bouyer wrote:
On Wed, Jul 23, 2014 at 08:46:34AM -0400, Thor Lancelot Simon wrote:
I just ordered a Supermicro low-power rackmount x86 machine which -- I
discovered after ordering it -- uses a Marvell 88SE9230 as a SATA controller.
>From FreeBSD's ahci.c, I see this i
And,
I put my slide of AsiaBSDCon 2014 Working In Progress session at:
http://www.netbsd.org/~msaitoh/Improving_MII_PHY.pdf
Thanks.
--
---
SAITOH Masanobu (msai...@execsw.org
msai...@netbsd.o
Hi.
(2014/02/15 1:58), Izumi Tsutsui wrote:
I'd suggest to clarify what problems you are trying to solve
and consider how it should be solved, before updating your patch.
The problems you mentioned are:
(1) merge initialization of sparse register mappings (with 4 byte stride)
Right.
(2) def
(2014/01/31 18:14), Martin Husemann wrote:
On Fri, Jan 31, 2014 at 12:59:15AM -0800, Matt Thomas wrote:
Why would anyone want this? Say you have a system in which the MMU can have
per translation table page sizes. a 16KB page size might be desirable for the
kernel and for LP64 processes. If y
(2013/11/20 0:02), Christoph Badura wrote:
After updating my -current kernel from 6.99.24 to 6.99.27 so I could
commit my ubsec(4) changes I noticed that under 6.99.27 I get between
3 and 8 percent less throughput on accelerated crypto ops.
Note that I am using the exact same ubsec(4) code[1] wi
Hello, Emmanuel.
(2013/07/04 12:35), Emmanuel Dreyfus wrote:
> SAITOH Masanobu wrote:
>
>> It's time for me to buy iMac... ;-)
>
> Did you have a look at the 57766 commit in Linux? There are a few 57766
> and 57665 specific things:
>
> http://code.google.com/p/linux-picosam9g45/source/diff?sp
(2013/07/03 15:51), Emmanuel Dreyfus wrote:
On Wed, Jul 03, 2013 at 03:03:11PM +0900, Masanobu SAITOH wrote:
I tested some cards and the jumbo frame function works if the
BGE_JUMBO_CAPABLE flags is set by the driver.
Please test if_bge.c rev. 1.254. It added the flag to some chips.
It
Hi, Emmanuel.
(2013/07/02 16:39), Emmanuel Dreyfus wrote:
On Mon, Jul 01, 2013 at 05:33:21PM +0900, Masanobu SAITOH wrote:
Could you compile a kernel with BGE_DEBUG and show me the dmesg?
Here it is:
Thanks.
I tested some cards and the jumbo frame function works if the
Hello, Emmanuel.
(2013/06/28 19:31), Emmanuel Dreyfus wrote:
Hi
New iMac have a broadcom 57766, which is handled out of the box by the
bge(4) driver in -current. The driver almosts treats it as a 57765,
which seems almost correct when looking at Linux driver contributed
by Broadcom:
http://code
Hi, all.
Without following patch. Some drivers which don't use link
interrput check the link status only every sc->mii_anegticks.
It's late. The patch is a part of FreeBSD's mii_physubr.c r158649:
http://svnweb.freebsd.org/base/head/sys/dev/mii/mii_physubr.c?r1=150756&r2=158649
Any objecti
(2013/06/03 11:41), Masanobu SAITOH wrote:
Hi.
The following patch fix a problem that a lot of phys misunderstand
the auto negotiation timer. Usually the autonegotiaton timer is set
to 10(MII_ANEGTICKS_GIGE), but a lot of dirver don't work as expected.
e.g.:
(mii_ticks
(2013/06/04 5:50), David Holland wrote:
On Mon, Jun 03, 2013 at 11:37:29AM -0400, Mouse wrote:
> At $JOB, we have two i386 machines with wm interfaces connected
> back-to-back with a short patch cable and a /30 subnet of 192.168. One
> is NFS-serving some disk space to the other over this
Hi.
The following patch fix a problem that a lot of phys misunderstand
the auto negotiation timer. Usually the autonegotiaton timer is set
to 10(MII_ANEGTICKS_GIGE), but a lot of dirver don't work as expected.
e.g.:
(mii_ticks == 0)
ifconfig bge0 media auto up
(after 2 seconds, the
Hi, all.
I sent the followin mail more than two years ago.
> http://mail-index.netbsd.org/tech-kern/2010/07/28/msg008613.html
As the starting point to solve this problem, I committed the change to
add SIOCGETHERCAP stuff.
Example:
> msk0: flags=8802 mtu 1500
> ec_capabilities=5
>
94 matches
Mail list logo
