On Mon, Jun 21, 2010 at 8:09 PM, Anjali Kulkarni wrote:
> Hi,
>
> As I understand, there are 2 flavors of the Marvel Yukon driver. One is for
> Yukon-I devices, and is called skgeinit, and other is for Yukon-II devices
> and called sky2 driver.
> Looking at the release notes for 7.0, it looks li
on 22/06/2010 00:34 Andriy Gapon said the following:
> gdb change - I'd rather do it via kld_current_sos,
> kld_relocate_section_addresses. I'd like to avoid changing common gdb code
> for
> a variety of reasons.
I came up with the following patch.
EXEC_P and DYNAMIC flags are bfd library equiva
I have the following simple DTrace script
% cat fbt_test.d
BEGIN
{
trace(kernel`my_kern_variable);
}
When I run the script I get the following error
dtrace: error on enabled probe ID 1 (ID 1: dtrace:::BEGIN): invalid kernel
access in action #1 at DIF offset 4
This is a FreeBSD 6.1 base (
On Wednesday 31 March 2010 14:52:53 Giorgos Keramidas wrote:
> On Tue, 30 Mar 2010 15:10:58 -0400, John Baldwin wrote:
> > On Tuesday 30 March 2010 11:48:58 am Giorgos Keramidas wrote:
> >> +.It Va DEBUG_FLAGS
> >> +Defines a set of debugging flags that will be used to build all
> >> userland +bin
I saw similar behaviour a couple of years ago when I switched from
using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules.
The problem ended up being a change in the linker script used by GNU
ld for linking kernel modules. It used to always put some magic
symbols used by the linker t
On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
> I saw similar behaviour a couple of years ago when I switched from
> using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules.
> The problem ended up being a change in the linker script used by GNU
> ld for linking kernel mod
This exit should not be 0, regardless of msdosfs or not.
Same for if the '.' dir entries do in fact have B/M/A/C times,
operations on those entries should update those times
accordingly, as subdirs do. RELENG_8. Thanks.
# newfs_msdos /dev/fd0
/dev/fd0: 2829 sectors in 2829 FAT12 clusters (512 byte
Hi,
I'm creating a new thread on this issue.
On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
> I saw similar behaviour a couple of years ago when I switched from
> using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules.
> The problem ended up being a change in the linker
On Wed, Jun 23, 2010 at 02:38:06AM +0200, Hans Petter Selasky wrote:
> It appears many kmods are broken because the linker is stripping away static
> data declared with the section attribute in FreeBSD 8.1-RC1.
>
>
>
> I added those lines to the LDFLAGS in Makefile.kmod in the cuse4bsd port
> m
I have the following senerio -
We need to build the kernel and world for multiple platforms
architectures (amd64, mips, ppc, etc). Initially we had a set
of shell scripts for the following:
-kernel-toolchain.sh
-kernel64.sh
-world64.sh
-bldpkg.sh
Which set the correct environm
on 23/06/2010 03:38 Hans Petter Selasky said the following:
> Hi,
>
> I'm creating a new thread on this issue.
>
> On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
>> I saw similar behaviour a couple of years ago when I switched from
>> using gcc 4.0.2 to gcc 4.3.0 to compile some out-
On Wednesday 23 June 2010 08:47:52 Andriy Gapon wrote:
> on 23/06/2010 03:38 Hans Petter Selasky said the following:
> > Hi,
> >
> > I'm creating a new thread on this issue.
> >
> > On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
> >> I saw similar behaviour a couple of years ago when I
12 matches
Mail list logo
